[ http://jira.codehaus.org/browse/MNG-2438?page=all ]
John Casey updated MNG-2438:
----------------------------
Fix Version: 2.0.5
we should probably get some resolution for this for 2.0.5, since it's a real
mess to debug. My order of preference for the solution is:
1. figure out how to be smarter about determining whether a metadata file
contains relevant info before merging it.
2. suppress metadata resolution from legacy repositories
> 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
> Type: Bug
> Components: Artifacts and Repositories
> Versions: 2.0.4
> Reporter: John Casey
> Fix For: 2.0.5
>
>
> 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
