> usePlugin 'war'
>
> task splitWar(type: War) {
> // include only the project dependencies (from previous example)
>
> // might also change the destination dir, or the war name, eg
> // classifier = 'split' or customname = 'split.war'
> }
>
> You can run gradle war to produce the standard war file, and gradle
> splitWar to produce the split war file.
>
Aaah. I didn't realize the war{} entry in a project using the War plugin
was just a task named 'war' of type War. Now I see that you can define
another task of type War (just giving it a unique name). Also crucial to my
understanding is that each task can have it's own set of dependencies. I
thought dependencies were only defined at the project level -not at the task
level. I'm working on a multi-project build file.
I have this working now. My web application project has two tasks of type:
War. However, as usual, this has led to another question. Both of these
War tasks add the same fileSet and zipFileSet. Instead of redefining each
fileSet/zipFileSet in each task, is there a way to define a common fileSet,
in either a separate method or at the project level? This way, each War
could just add the fileSet/ZipFileSet from the common method/project
properties.
Andrew
--
View this message in context:
http://www.nabble.com/Only-bundle-sub-project-jars-in-WAR--not-transitive-depencies-tp25965185p26114666.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
