Marcus Better wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

my build script uses the Jetty plugin, but I need it to use a newer Jetty version (6.1.19) than the one included in Gradle 0.8, in order to take advantage of new features (specifically the ProxyServlet.Transparent class).


In trunk, it's been updated to Jetty 6.1.21, so Gradle 0.9 will have the stuff you need.

But this isn't a real solution to the problem. We really need some general way for the build script to specify which version of a tool a given plugin should use, and some way for the plugin to specify which versions of the tool it will work with. This should be usable with custom plugins too.

How can I replace Gradle's version of Jetty with the one my build script 
specifies?

I don't think there's a good way to do this at the moment. The only option I can think of is to replace the jars in $gradleHome/libs.

Could you add a JIRA issue for this problem?

I have tried adding it to the buildscript dependencies:

buildscript {
    dependencies {
        classpath group: 'org.mortbay.jetty', name: 'jetty-util', version: 
'6.1.19'
    }
}

This works only partially since the old jars are still on the classpath. It now finds the ProxyServlet.Transparent class, but the ProxyServlet is loaded from Gradle's version, and it breaks because there is a small internal ABI incompatibility between the versions. So, I need a way to expunge Jetty 6.1.14 from the classpath entirely.

Cheers,

Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkrnJVkACgkQXjXn6TzcAQlZDwCeN4hUkL2HPTgjFIBKkeRV/T4/
vMUAn2hLNSvnrX8ZsphGkR3xCfe/x7DI
=5LAu
-----END PGP SIGNATURE-----



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



--
Adam Murdoch
Gradle Developer
http://www.gradle.org


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to