You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2007/09/14 21:16:32 UTC

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

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

Hadoop QA commented on HADOOP-1650:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12362491/hadoop-jetty6.1.4-lib.tar.gz
against trunk revision r575578.

    @author +1.  The patch does not contain any @author tags.

    patch -1.  The patch command could not apply the patch.

Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/766/console

This message is automatically generated.

> Upgrade Jetty to 6.x
> --------------------
>
>                 Key: HADOOP-1650
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1650
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>         Attachments: hadoop-jetty6.1.4-lib.tar.gz, jetty6.1.4.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.