[ 
http://jira.codehaus.org/browse/MANTTASKS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed MANTTASKS-18.
----------------------------------

    Resolution: Fixed

> filesetId does not contain all dependencies when artifact was not yet locally 
> installed
> ---------------------------------------------------------------------------------------
>
>                 Key: MANTTASKS-18
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-18
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>          Components: dependencies task
>    Affects Versions: 2.0.6
>         Environment: java version "1.4.2_04", Linux 2.6.11.12, Apache Ant 
> version 1.6.5
>            Reporter: Ingo Weichsel
>            Priority: Critical
>             Fix For: 2.0.7
>
>         Attachments: MANTTASKS-18_new.diff, MANTTASKS-18_new.tgz, 
> MANTTASKS-18_new2.diff, patch.txt
>
>
> In the artifact:dependencies task the filesetId is only correctly set, when 
> the artifact was installed locally before running ant. 
> After deletion of the local repository the dependant artifacts will be 
> downloaded to the local repository, but only one of two dependant files will 
> be included in the ant fileset. The classpath is set correctly.
> After running "mvn install" locally for the "as-base-launcher" maven project, 
> ant computes the correct filesetId.
> The ant-project depends on the artifact "as-base-launcher" which itselfs 
> depends only on classworlds. Snippets from ant buildfiles, poms and ant 
> output follows:
> From the ant buildfile:
> <target name="launcherJAR" depends="init">
> <artifact:pom id="as-base.project" file="../poms/as-base.xml" />              
>                                                                 
> <artifact:dependencies  filesetId="as-launcher.fileset" 
> pathId="as-launcher.classpath" verbose="true">
>       <pom refid="as-base.project"/>
>       <remoteRepository refid="actisRepository" />
> </artifact:dependencies>
> <pathconvert property="mypath" targetos="unix">
>       <path>
>               <path refid="as-launcher.classpath" />
>       </path>
> </pathconvert>
> <echo message="CLASSPATH: ${mypath}"/>
> <pathconvert property="myset" targetos="unix">
>       <path>
>               <fileset refid="as-launcher.fileset"/>
>       </path>
> </pathconvert>
> <echo message="FILESET: ${myset}"/>
> </target>
> The referenced POM defining the ant dependencies:
> <project>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>actis</groupId>
>   <artifactId>ant-as-base</artifactId>
>   <version>1.0-SNAPSHOT</version>
>   <dependencies>
>     <dependency>
>       <groupId>actis</groupId>
>       <artifactId>as-base-launcher</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>   </dependencies>
>   <repositories>
>     <repository>
>       <id>actisRepository</id>
>       <name>actisRepository</name>
>       <url>http://company.com:9999/repository/</url>
>     </repository>
>   </repositories>
> </project>
> Output of the ant run:
> launcherJAR:
> actis:ant-as-base:jar:1.0-SNAPSHOT (selected)
>   actis:as-base-launcher:jar:1.0-SNAPSHOT (selected)
>     classworlds:classworlds:jar:1.1-alpha-1 (selected)
>      [echo] CLASSPATH: 
> /home/iwe/.m2/repository/classworlds/classworlds/1.1-alpha-1/classworlds-1.1-alpha-1.jar:/home/iwe/.m2/repository/actis/as-base-launcher/1.0-20051103.102305-8/as-base-launcher-1.0-20051103.102305-8.jar
>      [echo] FILESET: 
> /home/iwe/.m2/repository/classworlds/classworlds/1.1-alpha-1/classworlds-1.1-alpha-1.jar

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to