[jira] Updated: (HADOOP-1650) Upgrade Jetty to 6.x

["Chris Douglas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated HADOOP-1650:
----------------------------------

    Attachment: 1650-0.patch

Merged patch with trunk, accommodating HADOOP-3854 and HADOOP-4284.

I used [jetty-6.1.12.rc4|http://dist.codehaus.org/jetty/jetty-6.1.12/jetty-6.1.12.rc4.zip] for this patch. Applying this patch, removing:
* lib/jetty-\*
* lib/servlet-api.jar
and adding
* lib/servlet-api-2.5-6.1.12.rc4.jar
* lib/jetty-6.1.12.rc4.jar
* lib/jsp-2.1
* lib/jetty-util-6.1.12.rc4.jar

Passes all unit tests on my machine. This is just a draft; it still needs to be benchmarked and the configuration of the Jetty components requires more thought.

> Upgrade Jetty to 6.x
> --------------------
>
>                 Key: HADOOP-1650
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1650
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>         Attachments: 1650-0.patch, 1650-20080120.patch, 1650-jetty6.1.9.patch, 1650-jetty6.1.9.v1.patch, hadoop-1650-jetty6.1.5.patch, hadoop-jetty6.1.4-lib.tar.gz, hadoop-jetty6.1.6-lib.tar.gz, hadoop-jetty6.1.9-lib.tar.gz, jetty-hadoop-6.1.6.patch, jetty-hbase.patch, jetty6.1.4.patch, jetty6.1.6.patch
>
>
> This is the third attempt at moving to jetty6. Apparently, the jetty-6.1.4 has fixed some of the issues we discovered in jetty during HADOOP-736 and HADOOP-1273. I'd like to keep this issue open for sometime so that we have enough time to test out things.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.