[
https://jira.codehaus.org/browse/MENFORCER-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343411#comment-343411
]
Robert Scholte commented on MENFORCER-190:
------------------------------------------
I don't like this rule. This would suggest that you can always do an auto
update of dependencies / parents. When such dependency has a serious bug you
don't want to use it, hence it will be blocking your release, especially if
we're talking about third party dependencies.
If a dependency works, there's no direct need to upgrade. Instead users could
use the [versions-maven-plugin|http://mojo.codehaus.org/versions-maven-plugin/]
every now and then to verify if they are up to date and give it a try first.
> Rule to guarantee that the newest released version of an artifact will be
> used.
> -------------------------------------------------------------------------------
>
> Key: MENFORCER-190
> URL: https://jira.codehaus.org/browse/MENFORCER-190
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
> Affects Versions: 1.3.1
> Reporter: Karl Heinz Marbaise
> Priority: Minor
>
> It would be nice having a rule which guarantees having always the newest
> release of the project dependencies.
> It would also handy having a configuration option to limit this to a
> particluar groupId/artifactId (may be wildcards)...
> {code}
> <requireNewestReleasedVersion>
> <transitive>true</transitive>
> <includes>
> <include>groupid:artifactId:*:bin:*</include>
> </includes>
> </requireNewestReleasedVersion>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
