bpmc/bpm-console — pull request #13 by jdcasey (2012-04-03 16:52:39+00:00)
Title: Split WAR production into multiple modules for 2.3.x branch

These commits refactor the old war/ module into four parts, plus one new parent POM:

Create a WAR module for each of {jbpm,riftsaw} (the outputs from the old war/ module).

Move the resources from profiles/{jbpm,riftsaw} into the appropriate WAR module, under the directory src/main/webapp (they're now webapp sources, not resources to be copied in multiple times).

Factored out the generated Version.java and GWT classes into war-base/ which is in the gui/ directory. This is a WAR overlay that is used by each war/* module.

Factored out the common templates into war-templates/ in the gui/ directory. This contains filterable templates that must be matched with a filter properties file to produce WAR-specific resources.

Moved/consolidated the properties used to filter above templates into a single properties file under src/main/properties for each WAR module. These are now specified in the / configuration of the POM.

NOTE: As far as I could, I consolidated common configuration for the WAR modules in the new war-parent POM (the one in wars/pom.xml). You'll find that each war module's POM contains very little configuration as a result.

ALSO: I simplified the list of plugins used, by generating the Version.java using the resources plugin to filter a java source file, then include it via the buildhelper plugin, just as before. This eliminates antrun from the mix.

I've checked the resulting WARs against the originals generated in the old structure, and the only differences appear to be included Maven POMs in META-INF, and generated cache files.