Appendix B. Writing Code

This chapter is intended for developers. There are no special prerequisites. Each part describes what a developer has to look at in specific for the OpenEngSB.

B.1. Maven POM files in the OpenEngSB

Following the guidelines of Maven Central, how a pom should be designed it is required to add the following tags into every and each pom file:

  • modelVersion
  • groupId
  • artifactId
  • version
  • packaging
  • name
  • description
  • url
  • licenses
  • scm/url
  • scm/connection
  • scm/developerConnection

The following listings shows an example of these params for a typical OpenEngSB pom.

<modelVersion>4.0.0</modelVersion>
<groupId>org.openengsb.core</groupId>
<artifactId>openengsb-core-parent</artifactId>
<version>1.1.0-SNAPSHOT</version>
<name>OpenEngSB :: Core :: Parent</name>
<packaging>pom</packaging>
<description>Parent project for all OpenEngSB Core classes</description>
<url>http://www.openengsb.org</url>
<licenses>
  <license>
    <name>Apache 2</name>
    <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
    <distribution>repo</distribution>
  </license>
</licenses>
<scm>
  <connection>scm:git:git://github.com/openengsb/openengsb.git</connection>
  <developerConnection>scm:git:git@github.com:openengsb/openengsb.git</developerConnection>
  <url>http://github.com/openengsb/openengsb</url>
</scm>