[ 
https://jira.codehaus.org/browse/MENFORCER-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343414#comment-343414
 ] 

Karl Heinz Marbaise commented on MENFORCER-190:
-----------------------------------------------

It was my first thought to create a enforcer rule of it. Maybe the idea is 
wrong and i should go for a plugin...

I have several projects where i have the situation using an artifact in a 
particular version let's say 1.0.5 which represents a product after several 
changes. This project which uses this artifacts produces a kind of  installer 
to distribute to test/production department. If test is successful everything 
is fine and done. But if there is bug found the artifact needs to be changed 
which means 1.0.6 is created. And afterwards the  installation projects needs 
to be updated. So a developer sometimes missed to update the version within the 
pom file to use the newest artifact which i could prevent via an enforcer rule 
and let the build break, but of course this installation artifact can change 
it's version from time to time if  only some configuration files/properties 
have been changed.

Apart from that the variant which Mirko describes came into my mind as well, 
cause i'm faced with the same problems.

But now it sounds more and more like a separate plugin than an enforcer rule. 
Thanks for your comments and ideas and hints.


> 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)

Reply via email to