Enhancement
Deploy aspects can be specified in the deployment, which are additionally built into the war file. There are the following disadvantages here:
- Only "deploy" aspects from the top-level folder are considered.
- If there is a deploy aspect with the same name in base modules, they will not be 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.
For each base module, first the "normal" web application, then "deploy/foo/webapp" from the base module and finally "deploy/bar/webapp" from the base module are copied into the WAR directory. Then the next higher module is processed. Neither "deploy/foo/webapp", nor "deploy/bar/webapp" need to exist in each module.
A special feature is the deploy aspect "local". This is only built into the WAR at the top level.
Test
- Deploy demo application
- Expectation: On the server, the tl_basic.bos.xml file exists and is entered into the metaConf.txt (comes from the "private" folder from com.top_logic.basic).
- Expectation: On the server the file ldapConf.bos.xml exists and is entered into the metaConf.txt (comes from the "private" folder from com.top_logic.demo).
- TL-Studio build.
- Expectation: Neither tl_basic.bos.xml nor ldapConf.bos.xml are present.
- Expectation: TL demo started normally.