On 1/6/2011 4:03 PM, Adam Murdoch wrote:
[snip] >
2. Get rid of the provided classpaths, and instead model the target environments. For a war, you'd define the target web container, which would include the provided classpath. This would allow you to build different wars for different target containers.
Just had to say, this one made me go "Oooooh" and nod my head a lot. -Paul
The war plugin would wire up some defaults, so that the war targets a generic web container with the appropriate servlet version. You'd then be able to configure that web container, or add others. This same definition would also be usable for deployment, too. The jetty plugin can use the web container definition to determine which version of jetty to use, and what to make available in the container classpath. -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
