[
http://jira.codehaus.org/browse/MENFORCER-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232101#action_232101
]
Herve Boutemy commented on MENFORCER-94:
----------------------------------------
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
> Review evaluation of version ranges with regard to inclusion of snapshots
> -------------------------------------------------------------------------
>
> Key: MENFORCER-94
> URL: http://jira.codehaus.org/browse/MENFORCER-94
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Task
> Components: Standard Rules
> Affects Versions: 1.0-beta-1
> Reporter: Benjamin Bentmann
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
