You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/30 20:59:55 UTC
[jira] Commented: (MNG-2438) search for metadata in legacy
repositories causes wrong repository source to be used for artifact
resolution
[ http://jira.codehaus.org/browse/MNG-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204601#action_204601 ]
Jason van Zyl commented on MNG-2438:
------------------------------------
Legacy repos go away in Maven 3.0, and most people don't use them in 2.0.
> search for metadata in legacy repositories causes wrong repository source to be used for artifact resolution
> ------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2438
> URL: http://jira.codehaus.org/browse/MNG-2438
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: John Casey
>
> legacy repositories store all version metadata in a single file under the /poms/ subdirectory of the artifactId dir. This means that snapshot resolution will result in the legacy repository being marked as the source for the artifact, regardless of whether that metadata file contains the snapshot is actually in that repository's metadata file or not. This is because the metadata manager (and metadata class itself, possibly) assumes that all metadata files resolved for a particular artifact/snapshot are relevant to that snapshot...when the legacy repo's metadata is merged into the rest of the in-progress metadata, changes are detected, and the legacy repo is adopted as the source for the latest artifact information, regardless of whether it actually contains information about that snapshot or not.
--
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