[
https://jira.codehaus.org/browse/MNG-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343188#comment-343188
]
Benjamin Podgursky commented on MNG-612:
----------------------------------------
Sorry to jump on an ancient ticket, but could you point me to how to modify
this behavior via Aether?
For context, I'm moving a bunch of projects from ivy to maven dependency
declarations, and it would be really helpful to at least temporarily emulate
ivy's "always choose newest" behavior so I don't have to manually hunt through
the dependency lists to make sure nothing is getting a different version than
it used to...
> implement conflict resolution techniques
> ----------------------------------------
>
> Key: MNG-612
> URL: https://jira.codehaus.org/browse/MNG-612
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Artifacts and Repositories, Design, Patterns & Best
> Practices
> Reporter: Brett Porter
> Assignee: Mark Hobson
> Priority: Critical
> Fix For: 3.x / Backlog
>
> Attachments: MNG-612-2.patch, MNG-612-3.patch, MNG-612.patch
>
> Original Estimate: 8 hours
> Remaining Estimate: 8 hours
>
> currently, the collector only:
> - selects nearest "suggested" version in a valid range
> - latest version from the valid ranges if none suggested
> - fails if ranges are over-constrained
> This needs to be configurable:
> - select newest, even if there is a nearer suggestion
> - select oldest, even if there is a nearer suggestion
> - fail if all suggestions don't equate or a range results instead of a single
> version
> - ignore over constrained ranges and fallback to some other algorithm
> - select snapshots even if they weren't explicitly specified
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
