hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8515) Upgrade Jetty to the current Jetty 7 release
Date Wed, 20 Jun 2012 16:32:42 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397615#comment-13397615

Steve Loughran commented on HADOOP-8515:

I can see the rationale for this, but I can also see that migration being somewhat traumatic.

# Is the migration from com.mortbay.jetty packages a simple package migrate, or are there
other consequences?

# does the jetty 7 stack have different dependencies? It's the reason SLF4j is currently pulled
> Upgrade Jetty to the current Jetty 7 release
> --------------------------------------------
>                 Key: HADOOP-8515
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8515
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Luke Lu
>              Labels: jetty
> According to http://dev.eclipse.org/mhonarc/lists/jetty-announce/msg00026.html, jetty-6
has been effectively EOL since January. Let's bump jetty to the 7 series. The current jetty
6.1.26 contains at least one known vulnerability: CVE-2011-4461.
> Note this can be an incompatible change if you reference jetty-6 packages (com.mortbay.jetty.*).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message