bpmc/bpm-console — pull request #9 by jdcasey (2012-03-23 21:12:13+00:00)
Title: Refactored WAR build

Refactored WAR build into multiple WAR builds plus two supporting modules (-war-templates and -war-base), to better support single-pass builds that produce all relevant WARs.

This work simply breaks up the old gui/war/ module into five parts:

1. war-base/ - module containing the GWT sources. This module produces a WAR file, but it's just meant to be an overlay that gets expanded and included in the real WAR builds.

2. war-templates/ - module containing resources that need to be filtered before inclusion in the WAR. These need special processing to handle the filtering, so couldn't be included in the war-base module.

3. wars/pom.xml - parent pom for wars, provides almost all of the plugin configuration for WAR building

4. wars/jbpm/ - JBPM WAR build, including filter properties (and config) specific to jbpm

5. wars/riftsaw/ - Riftsaw WAR build, including filter properties (and config) specific to riftsaw.

These will produce two WARs you'll be interested in: gwt-console-jbpm-.war, and gwt-console-riftsaw-.war. Their context paths should be unaltered, since those are filtered into the web.xml files.

I've verified the checksums of the files contained within the resulting WARs and compared them against the old approach. The only difference I can find is in generated variable names coming out of the GWT build.

If you approve of this new approach, I can also port it to whatever branch you need (2.3.x, for instance).