[jira] Moved: (MANTTASKS-133) indirect snapshot dependency not in fileset

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

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

Benjamin Bentmann moved MNG-1946 to MANTTASKS-133:
--------------------------------------------------

    Affects Version/s:     (was: 2.0)
                       2.0
          Component/s:     (was: Ant tasks)
                       dependencies task
                  Key: MANTTASKS-133  (was: MNG-1946)
              Project: Maven 2.x Ant Tasks  (was: Maven 2)

> indirect snapshot dependency not in fileset
> -------------------------------------------
>
>                 Key: MANTTASKS-133
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-133
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>          Components: dependencies task
>    Affects Versions: 2.0
>         Environment: Java 1.5
>            Reporter: Michael Hartmeier
>         Attachments: build.xml
>
>
> I use 
>    <artifact:dependencies filesetId="fileset">
>         <dependency groupId="myGroup" artifactId="first" version="0.86">
>         </dependency>
>         <artifact:remoteRepository url="http://myCompany/repository/">
>           <snapshots updatePolicy="always" enabled="true"/>
>           <releases updatePolicy="always" enabled="true"/>
>         </artifact:remoteRepository>
>       </artifact:dependencies>
> to fetch "first" and all dependent jar files. First's pom contains 
>     <dependency>
>       <groupId>myGroup</groupId>
>       <artifactId>second</artifactId>
>       <version>0.5-SNAPSHOT</version>
>     </dependency>
> Problem: the "second" jar file is in not in the fileset. 
> Note 1: Everything work's fine if "second"'s version is 0.5.
> Note 2: I can work-around the problem by adding a second dependencies call 
>     <artifact:dependencies filesetId="fileset.second">
>         <dependency groupId="myGroup" artifactId="second" version="0.5-SNAPSHOT">
>         </dependency>
>         <artifact:remoteRepository url="http://myCompany/repository/">
>           <snapshots updatePolicy="always" enabled="true"/>
>           <releases updatePolicy="always" enabled="true"/>
>         </artifact:remoteRepository>
>       </artifact:dependencies>
> to my build file (and use to fileset references). However, having a single dependencies 
> call with two dependency lines does *not* help.

-- 
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