hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-798) Exclude second Ant JAR from classpath in hdfs builds
Date Thu, 24 Feb 2011 03:56:38 GMT

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

Konstantin Boudnik commented on HDFS-798:

a similar fix is needed for MR, apparently (will open a separate issue for that)

> Exclude second Ant JAR from classpath in hdfs builds
> ----------------------------------------------------
>                 Key: HDFS-798
>                 URL: https://issues.apache.org/jira/browse/HDFS-798
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.22.0
>            Reporter: Steve Loughran
>            Assignee: Konstantin Boudnik
>            Priority: Minor
>         Attachments: HDFS-798.patch
> I've no evidence that this is a problem, but I have known it to be in different projects:
> {code}
>     [junit] WARNING: multiple versions of ant detected in path for junit 
>     [junit]          jar:file:/Users/slo/Java/Apache/ant/lib/ant.jar!/org/apache/tools/ant/Project.class
>     [junit]      and jar:file:/Users/slo/.ivy2/cache/ant/ant/jars/ant-1.6.5.jar!/org/apache/tools/ant/Project.class
> {code}
> Somehow Ivy needs to be set up to skip pulling in an old version of Ant in the build
-both paranamer-ant and jsp-2.1 declare a dependency on it. If both tools are only ever run
under Ant, the ivy.xml file could exclude it, the build file just has to make sure that Ant's
own classpath gets passed down.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message