Using

Maven usage

Note: x.y.z always denotes the version you need. See Home for the most current version.

Add the following to your pom.xml to use this artifact:

<dependency>
  <groupId>com.helger.phase2</groupId>
  <artifactId>phase2-lib</artifactId>
  <version>x.y.z</version>
</dependency>

For the MongoDB partnership factory, add the following to your pom.xml:

<dependency>
  <groupId>com.helger.phase2</groupId>
  <artifactId>phase2-partnership-mongodb</artifactId>
  <version>x.y.z</version>
</dependency>

For the receive servlet, add the following to your pom.xml:

<dependency>
  <groupId>com.helger.phase2</groupId>
  <artifactId>phase2-servlet</artifactId>
  <version>x.y.z</version>
</dependency>

For the standalone socket server, add the following to your pom.xml:

<dependency>
  <groupId>com.helger.phase2</groupId>
  <artifactId>phase2-server</artifactId>
  <version>x.y.z</version>
</dependency>

• Note: prior to v6.0.0 the Maven groupId was com.helger.as2.
• Note: prior to v4.6.0 the Maven groupId was com.helger.

Usage as Maven BOM

Alternatively you can use the parent POM as a BOM to have all dependencies included "automagically". Please note, that this only works inside the <dependencyManagement> part of your pom.xml:

  <dependencyManagement>
    <dependencies>
...
      <dependency>
        <groupId>com.helger.phase2</groupId>
        <artifactId>phase2-parent-pom</artifactId>
        <version>x.y.z</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
...
    </dependencies>
  </dependencyManagement>

• Note: prior to v6.0.0 the Maven groupId was com.helger.as2.
• Note: prior to v4.6.0 the Maven groupId was com.helger.