[ http://jira.codehaus.org/browse/MNG-1408?page=comments#action_84771 ]
Peter Murray commented on MNG-1408:
-----------------------------------
I have encountered this problem too, but have more to share on it. The failure
to properly use the SNAPSHOT part of the path to the file seems to be related
to when there is a definition of a <remoteRepository> in the ant build file.
<artifact:dependencies pathId="maven.dependencies"
filesetId="dependency.fileset">
<dependency groupId="com.tracegroup" artifactId="gui-tabs-and-docking"
version="1.0-SNAPSHOT"/>
<localRepository location="${basedir}/dependencies"/>
<remoteRepository refid="remote.repository"/>
</artifact:dependencies>
If the <remoteRepository> part was commented out (after the files were
downloaded to the local repository) the paths would use SNAPSHOT as expected
instead of the timestamp.
> filesetId does not contain all dependencies when artifact was not yet locally
> installed
> ---------------------------------------------------------------------------------------
>
> Key: MNG-1408
> URL: http://jira.codehaus.org/browse/MNG-1408
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks
> Affects Versions: 2.0
> Environment: java version "1.4.2_04", Linux 2.6.11.12, Apache Ant
> version 1.6.5
> Reporter: Ingo Weichsel
> Fix For: 2.0.x
>
> Attachments: 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
