major
minor
defect
major
minor
An application can be deployed in multiple "variants." Deployment should not require a rebuild of the application; instead, an application should be deployed to a container from its artifacts, which have been deployed to a Maven repository. To achieve this, it should be possible to create a (potentially temporary) deployment module in which the application is packaged into a runnable WAR (possibly with configuration adjustments) from its fragment WAR artifacts.
Procedure
Creating a Deployment Module
mvn -P tl-dev archetype:generate \ -DarchetypeGroupId=com.top-logic \ -DarchetypeArtifactId=tl-archetype-deploy \ -DarchetypeVersion=7.5.0-SNAPSHOT \ \ -DgroupId=com.top-logic \ -DartifactId=tl-demo-deploy \ -Dversion=7.5.0-SNAPSHOT \ \ -DappGroupId=com.top-logic \ -DappArtifactId=tl-demo \ -DappVersion=7.5.0-SNAPSHOT
Here, a deployment module with the coordinates com . top-logic : tl-archetype-deploy: 7.5.0-SNAPSHOT is created for the application com.top-logic: tl-demo :7.5.0-SNAPSHOT.
In this module, a WAR for the application can then be built, for example, by adding additional configurations:
cd tl-demo-deploy mvn -P with-h2 clean package
A *-app.war file containing the executable application (in this case, including the H2 database) is then created in the target folder.
See doc:war-deployment&uuid=e5dc1a13-a5f3-4298-820b-34a08d2fa266
Test
- Follow the instructions above.