[
http://jira.codehaus.org/browse/MNG-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99887
]
Wendy Smoak commented on MNG-3060:
----------------------------------
Have you considered using the enforcer plugin to make sure that projects are
built with the correct version of Maven?
See:
http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requireMavenVersion.html
> backwards compatible maven command line
> ---------------------------------------
>
> Key: MNG-3060
> URL: http://jira.codehaus.org/browse/MNG-3060
> Project: Maven 2
> Issue Type: New Feature
> Components: Command Line
> Reporter: Ryan Christianson
>
> I work for a company that is using maven 2.0.4. We are looking at upgrading
> to 2.0.6, but we have many projects that might be broken by the upgrade. This
> means that we need to upgrade all of our old projects, which its expensive.
> I'm wondering if this could be solved by updating the command line tool to
> support multiple installed versions of maven.
> It might work like this:
> - add a "suggested maven version" to pom.xml files (eg.
> <mavenVersion>2.0.4</mavenVersion>
> - update the mvn command line tool to look for the suggested version maven as
> class paths like this:
> - M2_HOME_2_0_4 would be maven 2.0.4, M2_HOME_2_0_6 would be 2.0.6 and so on.
> - if no M2_HOME_{$VERSION} is found, then use M2_HOME
--
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
