headers
Jesse McConnell | 17 Feb 2012 16:32
Picon
Gravatar

[jetty-announce] Jetty 7.6.1 and 8.1.1 released!

I have released an incremental update to the jetty 7.6 and 8.1
releases from a few weeks back.

Eclipse:
http://download.eclipse.org/jetty/

Codehaus:
http://dist.codehaus.org/jetty/

Of particular note in these releases are a fix to usage of the --exec
in the start.ini, it was largely broken in the last release generating
some incorrect paths and then a few fixes to the nosql mongo session
handling.

cheers,
jesse

jetty-7.6.1.v20120215 - 15 February 2012
 + 369121 simplified test
 + 370120 jvm arguments added via start.ini and --exec are missing spaces
 + 370137 SslContextFactory does not respect order for
   [included|excluded]Protocols() and [included|excluded]CipherSuites().
 + 370368 resolve stack overflow in mongo db session manager
 + 370386 Remove META-INF from jetty distro
 + 371040 nosqlsession needs to call correct super contructor for new sessions
 + 371041 valid was not being set to new mongo db sessions, and the call to
   mongodb api was wrong in isIdInUse
 + 371162 NPE protection for nested security handlers
 + JETTY-1484 Add option for HashSessionManager to delete session files if it
   can't restore them
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jesse McConnell | 18 Feb 2012 01:14
Picon
Gravatar

[jetty-announce] Re: Jetty 7.6.1 and 8.1.1 released!

Heads up...

Something I should have mentioned on this release is that we have
addressed some build issues we had regarding signed jars in eclipse
orbit that we had to pull in for distribution.  These dependencies
used to be pulled into the jetty-distribution through some ant magic
and have not been what was referenced via maven transitive
dependencies.  If you only use the jetty-distribution or
jetty-hightide, you can stop reading now.

If you use jetty via maven or especially if you explode the
dependencies via the maven dependency plugin you will likely see an
issue about signed classes.  This might come out of now where and
surprise you.  You should be able to just exclude the ECLIPSE.RSA and
ECLIPSE.SF files and be fine.  Or you can exclude the
org.eclipse.jetty.orbit groupId from the transitive dependencies and
track down unsigned dependencies manually.

For some more history you can see this issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=371954

Thanks to bubbleguuum for pointing this out!
jesse

--
jesse mcconnell
jesse.mcconnell <at> gmail.com

On Fri, Feb 17, 2012 at 09:32, Jesse McConnell
<jesse.mcconnell <at> gmail.com> wrote:
(Continue reading)

Permalink | Reply | 0 comments |

Gmane