...
| Code Block | ||
|---|---|---|
| ||
<profiles>
<profile>
<!-- This profile bundles a mock National Connector interface -->
<id>national-connector-mock-impl</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<dependencies>
<dependency>
<groupId>eu.epsos.protocolterminators.ws.server</groupId>
<artifactId>epsos-ws-server-mock-impl</artifactId>
<version>0.1.0</version>
<scope>runtime</scope>
</dependency>
</dependencies>
</profile>
<profile>
<!-- This profile bundles the country-specifig National Connector interface -->
<id>national-connector-impl</id>
<dependencies>
<dependency>
<groupId>${national-connector-interface.groupid}</groupId>
<artifactId>${national-connector-interface.artifactid}</artifactId>
<version>${national-connector-interface.version}</version>
<scope>runtime</scope>
</dependency>
</dependencies>
</profile>
</profiles> |
The first profile (activated by default) bundles the mock implementations into the war file. The second profile will bundle the National implementation. a National implementation. If no profile is specified then no implementation will be bundled into the jar. In this case, the jar must be deployed to the tomcat/lib directory.
For the National build to work it is necessary to configure the build environment with properties. These properties are defined in local configuration files:
...
| Code Block | ||
|---|---|---|
| ||
# build epsos-ws-serverwith no implementation mvn clean install # build epsos-ws-server with mock implementationimplementations mvn clean install -P national-connector-mock-impl # build epsos-ws-server with real implementationimplementations mvn clean install -P national-connector-impl |
...