Major
Detail
Bugfix
Major
Detail
An application can be deployed in multiple "flavors". For the deployment no rebuild of the application should be necessary, but an application should be deployed from its artifacts, which were deployed into a Maven repository, into a container. For this purpose, an (optionally temporary) deploy module should be able to be created, in which the application is packed into a runnable WAR (possibly with configuration adjustments) (from its fragment WAR artifacts).
Procedure
Create a deploy 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 deploy 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 be built, e.g. with the addition of further configurations:
cd tl-demo-deploy mvn -P with-h2 clean package
A *-app.war with the executable application (in this case including the H2 database) is then created in the target folder.
Siehe doc:war-deployment&uuid=e5dc1a13-a5f3-4298-820b-34a08d2fa266
Test
- According to the instructions above.