Maven 2 & 3

Managed versions dont affect over constrained ranges

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.8, 3.0-alpha-1, 3.0
  • Fix Version/s: 2.0.9
  • Component/s: Dependencies
  • Labels:
    None
  • Number of attachments :
    0

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

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

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.