[MENFORCER-94] Review evaluation of version ranges with regard to inclusion of snapshots

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0-beta-1
• Component/s: Standard Rules
• Assignee: Unassigned
• Reporter: Benjamin Bentmann
• Created: 09/Apr/10 14:08
• Updated: 19/Dec/19 12:12
• Resolved: 19/Dec/19 12:11

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.

Issue Links

• is related to: MNG-3092 Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
• is related to: MENFORCER-101 Enforcer does not allow to restrict based on SNAPSHOT version as version comparison uses artifact.getVersion() instead of artifact.getBaseVersion()
• is related to: MRELEASE-216 Release plugin should ignore SNAPSHOTS that are not specified in the POM
• relates to: MNG-4751 Snapshot version not resolved for version range