[
https://issues.apache.org/jira/browse/HADOOP-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397850#comment-13397850
]
Luke Lu commented on HADOOP-8515:
---------------------------------
bq. Is the migration from com.mortbay.jetty packages a simple package migrate,
or are there other consequences?
See: http://wiki.eclipse.org/Jetty/Starting/Porting_to_Jetty_7
A quick find/grep reveals that there are 30 (13 test source files) source files
in branch-1, 36 (17 test) in trunk, reference mortbay. Besides things in
HttpServer.java, it seems to be a simple package migrate.
bq. does the jetty 7 stack have different dependencies? It's the reason SLF4j
is currently pulled in
http://mvnrepository.com/artifact/org.eclipse.jetty/jetty-server/7.6.4.v20120524.
slf4j (which rocks btw :)) is still there.
> 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
