[
https://jira.codehaus.org/browse/MENFORCER-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343417#comment-343417
]
Robert Scholte commented on MENFORCER-190:
------------------------------------------
forcing the newest parent is almost as dangerous, but probably easier to
control (assuming you can fix this quite fast). In all these cases I think that
the answer lies in a good repository manager, which can analyze the pom during
the deploy. Based on a blacklist of parent-, dependency- and plugin versions it
can accept or block the artifact.
> 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)
