[
http://jira.codehaus.org/browse/MVERSIONS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189637#action_189637
]
Tuomas Kiviaho commented on MVERSIONS-6:
----------------------------------------
If I understood correctly, this goal would help with super-pom scenario where
while prior release one could have
<plugin>
<artifactId>maven-invoker-plugin</artifactId>
..
<plugin>
and when releasing this plugin would stamp the pom with whatever version is the
newest.
<plugin>
<artifactId>maven-invoker-plugin</artifactId>
<version>1.3</version>
..
<plugin>
This might not always be desired since if/when 1.4 comes out prior next maven
release (=super-pom) the intended version might not be 1.4 but 1.3 that the
used maven environment provided. Maybe an option (whether or not prefer
super-pom version over available versions) would be in order. I don't know if
release plugin already has this kind of feature.
> apply-plugin-updates goal
> -------------------------
>
> Key: MVERSIONS-6
> URL: http://jira.codehaus.org/browse/MVERSIONS-6
> Project: Maven 2.x Versions Plugin
> Issue Type: Improvement
> Reporter: Stephen Connolly
> Priority: Minor
> Fix For: 1.1
>
>
> This goal would check for any available plugin updates and if there are any
> it would:
> 1. Rename current pom.xml to pom.xml.original
> 2. Add a pluginManagement section (if none exists)
> 3. Update the plugin versions (using the pluginManagement section)
> This goal should only touch those plugins who's versions are not controlled
> by a parent (but if controled by the super-pom that's fine to update)
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
