In the deployment, you can specify deployment aspects that are additionally included in the WAR file. This has the following drawbacks:
- Only "deploy" aspects from the top-level folder are taken into account.
- If there is a deploy aspect with the same name in base modules, these are not taken into account.
How It Works
If the ${war.deploy.dirs} property is set during deployment, e.g., to "foo, bar," the "deploy/foo/webapp" and "deploy/bar/webapp" folders from each module are included in the web application.
In this process, for each base module, the “normal” web application is copied to the WAR directory first, followed by “deploy/foo/webapp” from the base module, and finally “deploy/bar/webapp” from the base module. Then the next higher-level module is processed. Neither "deploy/foo/webapp" nor "deploy/bar/webapp" need to exist in every module.
One special feature is the "local" deployment aspect. This is included in the WAR only at the top-level.
Test
- Deploying the Demo Application
- Expected: The file tl_basic.bos.xml is present on the server and listed in metaConf.txt (it comes from the “private” folder in com.top_logic.basic).
- Expected: The file ldapConf.bos.xml is present on the server and listed in metaConf.txt (it comes from the "private" folder in com.top_logic.demo).
- Build TL-Studio.
- Expected: Neither tl_basic.bos.xml nor ldapConf.bos.xml is present.
- Expected: TL-Demo starts normally.