[
https://jira.codehaus.org/browse/MRELEASE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-479.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
Let's not code this at several diffirent places. As Brett said, the enforcer
has the
[requirePluginVersions|http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html]
rule, which already does this.
Another reason to use the enforcer-plugin: it can check it with every build, so
you won't be surprized during the release.
> Option to handle plugins missing explicit version number
> --------------------------------------------------------
>
> Key: MRELEASE-479
> URL: https://jira.codehaus.org/browse/MRELEASE-479
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: prepare
> Affects Versions: 2.0-beta-9
> Reporter: Tuomas Kiviaho
> Assignee: Robert Scholte
>
> A plugin declaration without version number is likely to turn 'bad' when
> using other version of maven (and super-pom). A switch that prompts version
> number providing version from super-pom as default would prevent maven
> upgrades from corrupting builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
