hadoop-hdfs-issues mailing list archives

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

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

Steve Loughran commented on HDFS-798:
-------------------------------------

That will eliminate the complaint, but I now worry that ant core is needed for the eclipse
javac compiler that jsp2.1 uses. It may be safest to ignore the complaint to ensure that the
runtimes are set up right, and ensure that the version of ant that is added is the same version
that the project is built with.

FWIW, my ivy dependencies for jsp do pull in a version of ant, so that it gets passed down
the chain, with a separate JSP config that includes everything that JSP pages need: 
{noformat} 
    <dependency org="org.mortbay.jetty"
        name="jetty"
        rev="${jetty.version}"
        conf="compile->master;redist->master"/>
    <dependency org="org.mortbay.jetty"
        name="jetty-util"
        rev="${jetty.version}"
        conf="compile->master;redist->master"/>

    <!-- logging-->
    <dependency org="org.smartfrog"
        name="sf-loggingservices"
        changing="true"
        rev="latest.integration"
        conf="compile,runtime,jsp->default;redist->redist"/>    
    
    <!--JSP support -->
    <dependency org="org.mortbay.jetty"
        name="jsp-2.1"
        rev="${jetty.jsp.version}"
        conf="jsp->master"/>
    <dependency org="org.mortbay.jetty"
        name="jsp-api-2.1"
        rev="${jetty.jsp.version}"
        conf="jsp->master"/>
    <dependency org="commons-el"
        name="commons-el"
        rev="${commons-el.version}"
        conf="jsp->master"/>
    <!--this is the compiler stage-->
    <dependency org="org.smartfrog"
        name="sf-ant"
        rev="latest.integration"
        conf="jsp->default"/>
    <dependency org="org.eclipse.jdt"
        name="core"
        rev="${org.eclipse.jdt.core.version}"
        conf="jsp->master"/>
{noformat} 


> 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

        

Mime
View raw message