|

»

codehaus - Gradle

»

using a different Jetty version in build script

View: New views

4 Messages — Rating Filter: Alert me

	using a different Jetty version in build script by Marcus Better :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message -----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). How can I replace Gradle's version of Jetty with the one my build script specifies? 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
	Re: using a different Jetty version in build script by Adam Murdoch-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message 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
	Re: using a different Jetty version in build script by LightGuard :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Tue, Oct 27, 2009 at 18:27, Adam Murdoch <a@...> wrote: > > > 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. > This will typically work, however, if you're moving major versions you could run into issues like with Jetty a move from 6 to 7 would need a rewrite of the plugin as the package structure has changed. I'm not sure the best way to handle this. We could something like jetty6-plugin and a jetty7-plugin. Seems like there should be something better, but there may not be. >> 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 > > > -- Jason Porter Real Programmers think better when playing Adventure or Rogue. PGP key id: 926CCFF5 PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5 PGP key available at: keyserver.net, pgp.mit.edu --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
	Re: using a different Jetty version in build script by Marcus Better :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam Murdoch wrote: > Could you add a JIRA issue for this problem? Done, GRADLE-723. Cheers, Marcus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrp8KwACgkQXjXn6TzcAQn93gCfcw1fXpjY7MXPAsGG6m4a4FcW EzAAnisJRJueHFO4lt+Tnxj+0ZuyVoAN =gpDy -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email