Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
1.0-beta-1
-
None
-
None
Description
The fix for MNG-3092 affects also certain Enforcer rules that deal with version ranges. We need to review which rules are intended to match core's dependency resolution semantics and which rules deliberately want to include snapshots in version ranges. For instance, the rule RequireMavenVersion in combination with a range like [2.0.9,) now fails when run with Maven 3.0-SNAPSHOT which is counter-intuitive in this case.
Attachments
Issue Links
- is related to
-
MNG-3092 Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
- Reopened
-
MENFORCER-101 Enforcer does not allow to restrict based on SNAPSHOT version as version comparison uses artifact.getVersion() instead of artifact.getBaseVersion()
- Closed
-
MRELEASE-216 Release plugin should ignore SNAPSHOTS that are not specified in the POM
- Closed
- relates to
-
MNG-4751 Snapshot version not resolved for version range
- Closed
perhaps the version range algorithm should accept every snapshots when no upper-bound limit is set: when a range does not precisely know its target version, this snapshot restrictions can't apply
this would fix this precise case where version ranges are used for RequireMavenVersion rule, I don't know if this would be ok for other use