I'd be inclined to have a three projects: one that built war #1, one
that built war #2, and one solely responsible for merging the two
using something like:
war {
from zipTree(war1Project.war.archivePath)
from zipTree(war2Project.war.archivePath)
}
But I tend to prefer istinct subprojects over tasks/source sets/etc.,
and other people might suggest an alternative approach with a single
project and some configuration to wire things together.
~~ Robert.
On Wed, May 18, 2011 at 10:41 AM, mraccola <[email protected]> wrote:
> I need to convert an existing build that uses "WAR overlaying" to merge the
> contents of two web projects into one WAR. Think..one web project that has
> some framework stuff and then another web project that contains stuff that
> extends the framework stuff. The projects will both be modules in the same
> multi-module Gradle build.
>
> I think this should be fairly straight forward but I wanted to ask if there
> are any best practices for implementing this before I get started. If
> anyone has some script snippets that they can share that would also be
> appreciated.
>
> --
> View this message in context:
> http://gradle.1045684.n5.nabble.com/WAR-Overlay-tp4406652p4406652.html
> Sent from the gradle-user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
