hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9650) Update jetty dependencies
Date Fri, 05 Jul 2013 22:17:48 GMT

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

Alejandro Abdelnur commented on HADOOP-9650:

[~t.st.clair], typically we move up on versions of dependencies because of a bugfix that is
affecting us or because a new feature we want to use.

Otherwise we stick to the version we have for the following reasons:

* known stability
* potential incompatibilities either API or behavior
* transitive dependencies issues (we need to re-curate all transitive deps we exclude. historically
jetty has used their own groupId/artifactId for servlet/jsp, and they've change their names
across versions, that is a mess).

Furthermore, this particular change, is not just an update of the POM, it modifies the code
of hadoop as well.

Also, downstream projects, ie HBase that use stuff from Hadoop built on top of jetty will
most likely break.

So, unless there is something we really need from jetty9 I would be extremely cautious about
changing its version when we are trying to get Hadoop 2 stable to claim GA.
> Update jetty dependencies 
> --------------------------
>                 Key: HADOOP-9650
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9650
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 2.1.0-beta
>            Reporter: Timothy St. Clair
>              Labels: build, maven
>         Attachments: HADOOP-9650.patch, HADOOP-trunk-9650.patch
> Update deprecated jetty 6 dependencies, moving forwards to jetty 8.  This enables mvn-rpmbuild
on Fedora 18 & > platforms. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message