Yes, exactly. It's a nice feature of Maven (probably the only one) :-) 2011/3/22 Magnus Rundberget <[email protected]>
> Never used it myself, but I guess this sort of covers it ? > http://maven.apache.org/plugins/maven-war-plugin/overlays.html > > regards > Magnus > > > Date: Tue, 22 Mar 2011 11:18:54 -0700 > > From: [email protected] > > To: [email protected] > > Subject: [gradle-user] Re: War dependency to another war > > > > > A dependency from a War project to a War project doesn't work as expected > at > > the moment (there is an issue for it). Is there anything preventing you > from > > factoring out the common parts into a Jar project? I guess you'd have to > > find a solution for the shared webapp resources. Does Maven really allow > you > > to share webapp resources out-of-the-box? > > > > -- > > Peter Niederwieser > > Developer, Gradle > > http://www.gradle.org > > Trainer & Consultant, Gradleware > > http://www.gradleware.com > > Creator, Spock Framework > > http://spockframework.org > > > > > > Sten Roger Sandvik-2 wrote: > > > > > > Hi. > > > > > > I'm trying to figure out the best way to manage dependencies between > war > > > files. I have the following scenario: > > > > > > 1. A war project called 'common' that includes alot of dependencies and > > > webapp resources. > > > 2. A war project called 'specialized' that includes should be based on > > > 'common' and include all dependencies + specialized dependencies. And > > > specialized webapp resources. > > > > > > When using maven it worked out of the box. How could I do this in > Gradle? > > > > > > BR, > > > Sten Roger > > > > > > > -- > > View this message in context: > http://gradle.1045684.n5.nabble.com/War-dependency-to-another-war-tp4257270p4257342.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 > > > > >
