[
http://jira.codehaus.org/browse/MERCURY-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174281#action_174281
]
Oleg Gusakov commented on MERCURY-117:
--------------------------------------
My English - sorry.
What is meant: if a virtual version, in particular - snapshot, is found in the
*sufficient* repository, it should win, despite the fact that other
repositories down the search chain may contain a newer snapshot.
There is a moot point about ranges - right now I don't think this flag should
affect ranges, but what if the range is [2.0,2.1) and such repository contains
2.1-SNAPSHOT. Should this snapshot win? As I said - I don't think it should for
ranges.
Also - the term *sufficient* - is open for discussion. I was thinking about
*final* or *alwaysLatest*
> allow "sufficient" repositories
> -------------------------------
>
> Key: MERCURY-117
> URL: http://jira.codehaus.org/browse/MERCURY-117
> Project: Mercury
> Issue Type: New Feature
> Components: Repository
> Affects Versions: 1.0-alpha-8
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> Some repositories need to declare that artifacts found in them are final, and
> the virtual repository reader should stop scanning repositories for more.
> Apparent application is Maven's Reactor repository: if an artifact is found
> there, it is final and should be used over any other.
> This can be achieved by:
> * adding this repository to the front of the repository chain
> * declaring this repository "sufficient"
--
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
