Maven Enforcer Plugin
  1. Maven Enforcer Plugin
  2. MENFORCER-94

Review evaluation of version ranges with regard to inclusion of snapshots

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0-beta-1
    • Fix Version/s: None
    • Component/s: Standard Rules
    • Labels:
      None
    • Number of attachments :
      0

      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

          Activity

          Hide
          Herve Boutemy added a comment -

          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

          Show
          Herve Boutemy added a comment - 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
          Hide
          Herve Boutemy added a comment -

          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

          I have found the answer: no, this would not be ok because MRELEASE-216 has the exact contrary requirements

          Show
          Herve Boutemy added a comment - 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 I have found the answer: no, this would not be ok because MRELEASE-216 has the exact contrary requirements

            People

            • Assignee:
              Unassigned
              Reporter:
              Benjamin Bentmann
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: