Well, Maven uses something they call WebApp overlays. It's not great, but it
works. At least for small projects :-) What I want Gradle to do is the
following:

  * Common webapp project builds as usual (no magic stuff here)
  * Specialized webapp has sourceSets to itself and to the common webapp.
  * Specialized webapp has dependencies from common webapp and additional
dependencies.
  * Specialized webapp adds common webapp compiled classes/resources and
it's own compiled classes/resources.

Anyone have done something like this?


2011/3/22 Peter Niederwieser <[email protected]>

> 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
>
>
>

Reply via email to