You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/04/09 04:53:46 UTC

[jira] Moved: (MANTTASKS-49) Ant dependencies task does not work with multiple repositories

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

Brett Porter moved MNG-1466 to MANTTASKS-49:
--------------------------------------------

    Affects Version/s:     (was: 2.0.1)
                           (was: 2.0)
                       2.0
                       2.0.1
        Fix Version/s:     (was: 2.0.1)
                       2.0.1
          Component/s:     (was: Ant tasks)
           Complexity:   (was: Intermediate)
                  Key: MANTTASKS-49  (was: MNG-1466)
              Project: Maven 2.x Ant Tasks  (was: Maven 2)

> Ant dependencies task does not work with multiple repositories
> --------------------------------------------------------------
>
>                 Key: MANTTASKS-49
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-49
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>    Affects Versions: 2.0.1, 2.0
>         Environment: Maven 2.0, Maven 2.0 CVS
>            Reporter: Konstantin Ignatyev
>            Assignee: John Casey
>             Fix For: 2.0.1
>
>         Attachments: id.diff, id2.diff
>
>
> The maven-dependencies task for Ant cannot work properly with multiple repositories because it incorrectly hardcode artifact repository ID that causes all the repositories cache informatioon in the same file
> AbstractArtifactTask#
> .... 
> artifactRepository = repositoryFactory.createArtifactRepository( "remote", repository.getUrl(),
>                                                                             repositoryLayout, snapshots, releases );
> creates all the repositories with the same ID="remote" and that causes all the meta-information for all the repositories collide in one file because the file name pattern is:${gtoupId}/${artifactId}/maven-metadata-${repositoryId}.xml
> This causes whole thing work incorrectly.
> When Maven itself constructs ArtifactRepository, it properly assigns ID to the repository and the schema works.

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