[ https://issues.apache.org/jira/browse/HDFS-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik resolved HDFS-798. ------------------------------------- Resolution: Won't Fix People are concerned about some weird side-effects that this fix has in Eclipse environment. > 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. 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