[MNG-3396] Managed versions dont affect over constrained ranges

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.8, 3.0-alpha-1, 3.0
• Fix Version/s: 2.0.9
• Component/s: Dependencies
• Assignee: Carlos Sanchez Gonzalez
• Reporter: Carlos Sanchez Gonzalez
• Created: 10/Feb/08 23:00
• Updated: 12/Jun/08 17:50
• Resolved: 10/Feb/08 23:06

Description

If a dependency in the graph has a range [1.0, 2.0] and there's no version in the repo to satisfy it, a OverConstrainedVersionException is thron in the DefaultArtifactCollector
If you try to force a version out of the range in the dependencyManagement it is ignored.

Issue Links

• is related to: MNG-2123 NullPointerException when a dependency uses version range and another uses an actual version incompatible with that range
• is related to: MNG-3410 Managed versions in plugins are not considered when using them