Peter Lynch
added a comment - 04/15/12 08:06 PM - edited This seems to involve backporting https://github.com/sonatype/nexus/pull/297/ into nexus-2.0.x branch (from NEXUS-4852 ) and then bumping jetty version to latest Jetty 7 ( 7.6.2.v20120308 )
Also requires backporting https://github.com/sonatype/nexus-enterprise/pull/140 as well into nexus-enterprise-2.0.x branch.
Done this locally but needs a full IT test run at minimum yet to be done.

Peter Lynch
added a comment - 04/16/12 02:01 PM From stuart:
There were some test stability fixes that were put in after we moved master to Jetty8 that could also apply to Jetty7:
https://github.com/sonatype/nexus/pull/304
https://github.com/sonatype/nexus/pull/310
But these fixes (apart from the Jetty8 bump) are test specific and therefore don't need to be backported to 2.0.x
However, make sure you pick up the latest (sisu)plexus-jetty7 that contains a shutdown fix:
https://github.com/sonatype/nexus/pull/326
This issue wasn't seen in production, but it could conceivably happen so the version bump is worth backporting

backported all the relevant jetty7 upgrades from master that I could find, plus a few tweaks ( which I may need to forward port). pull 304 was already in nexus-2.0.x, pull 310 was too jetty8 focused and I could not find anything jetty7 to isolate, pull 326 was brought in to fix possible shutdown bug + all the others in my first comment added

Peter Lynch
added a comment - 04/16/12 09:37 PM - edited https://github.com/sonatype/nexus/pull/374
https://github.com/sonatype/nexus-enterprise/pull/196
backported all the relevant jetty7 upgrades from master that I could find, plus a few tweaks ( which I may need to forward port). pull 304 was already in nexus-2.0.x, pull 310 was too jetty8 focused and I could not find anything jetty7 to isolate, pull 326 was brought in to fix possible shutdown bug + all the others in my first comment added