On Mon, 29 Dec 2008 22:41:12 +0000, "Eric Bowman" <[email protected]> said: > Levi Hoogenberg wrote: > > Hello, > > > > no, my application doesn't depend on Jetty at all. The only thing that > > I can think of is that I'm using a 2.5 deployment descriptor. > > > > Declaring the dependency as a providedCompile one works, I forgot to > > mention that in my e-mail. > > I had the same problem with a 2.5 web.xml. > > I stuck this in settings.gradle to fix it: > > addMavenRepo() > dependencies( > "org.mortbay.jetty:jetty:6.1.14", > "org.mortbay.jetty:jetty-annotations:6.1.14", > "org.mortbay.jetty:jetty-plus:6.1.14", > "org.mortbay.jetty:jetty-util:6.1.14", > "org.mortbay.jetty:jetty-naming:6.1.14", > ) >
This works because the classpath of the Jetty Plugin is not properly isolated against the Gradle classpath yet. It has the same effect as adding the jars to the libs folder. It should suffice though, to add just the jetty annotations jar. In a future version of Gradle this would not work. I reccommend to add the dependencies via the providedCompile conf. Anyway, in the next release jetty annotations will be automatically added. We will also improve the documentation for the plugin. - Hans > > -- > Eric Bowman > Boboco Ltd > [email protected] > http://www.boboco.ie/ebowman/pubkey.pgp > +35318394189/+353872801532 > > > --------------------------------------------------------------------- > 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
