Since we now a install/update mechanism built in Magnolia, we're not going to deliver pre-bootstrapped wars anymore (future versions will allow selecting of options when installing)

However, we still need to reorganize the bundle mechanism so that:

• the webapp does not contain dms, samples and workflow, by default. Makes it easier to 3rd projects to depend on magnolia, and use magnolia-webapp as a "base" war on which they can overlay their stuff.
• the webapp is called magnolia-empty-webapp and not just "magnolia". Makes the artifact easier to identify.
• this webapp can go back to the default reactor build.

We'll create a new svn location where:

• we'll have a secondary webapp, which is magnolia-empty-webapp+magnolia-module-samples+magnolia-module-dms (no more ugly assembly hacks)
• the bundle will be called "magnolia-tomcat-bundle"

This helps keeping the main project clean, and makes them releasable independently.

Still subject to discussion:

• the bundle will either have the workflow module (with its dependencies) in a separate jar, or just a note pointing to a webpage listing the existing modules.
• the secondary webapp could be called "magnolia-sample-module" (our first idea) or "magnolia-bundled-webapp" (just an idea now)
• do we ship bundles for jdk14 and jdk15, given that the only difference is the inclusion of the tomcat-5.5-compat package, for 1.4, or do we let people deal with this on their own ?