[jira] Commented: (MRELEASE-479) Option to handle plugins missing explicit version number
[ http://jira.codehaus.org/browse/MRELEASE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=189949#action_189949 ] Brett Porter commented on MRELEASE-479: --- This type of tooling already exists in the enforcer and versions plugin... Option to handle plugins missing explicit version number Key: MRELEASE-479 URL: http://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 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-479) Option to handle plugins missing explicit version number
[ http://jira.codehaus.org/browse/MRELEASE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=189642#action_189642 ] Joerg Schaible commented on MRELEASE-479: - While this is true in general, there are exceptions. E.g. it does indeed make sense to use latest maven-help-plugin, maven-eclipse-plugin, ... Option to handle plugins missing explicit version number Key: MRELEASE-479 URL: http://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 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-479) Option to handle plugins missing explicit version number
[ http://jira.codehaus.org/browse/MRELEASE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=189668#action_189668 ] Tuomas Kiviaho commented on MRELEASE-479: - Using maven-eclipse-plugin type of plugin for released artifacts goes beyond my imagination :-) What about sticking to plugins that have explicit configuration in the pom at hand and leaving undeclared plugins as-is. Option to handle plugins missing explicit version number Key: MRELEASE-479 URL: http://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 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
