[ http://jira.codehaus.org/browse/MNG-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4774. ---------------------------------- Resolution: Not A Bug Assignee: Benjamin Bentmann I verified that Maven 3.0-beta-1 and -beta-2 run properly with cygwin, so this appears to be a mvnsh issue which should be filled at https://issues.sonatype.org/browse/MVNSH instead. > Setting MAVEN_OPTS adds new lifecycles to be executed > ----------------------------------------------------- > > Key: MNG-4774 > URL: http://jira.codehaus.org/browse/MNG-4774 > Project: Maven 2 & 3 > Issue Type: Bug > Affects Versions: 3.0-beta-2 > Reporter: ccadete > Assignee: Benjamin Bentmann > > If MAVEN_OPTS is set like this: > export MAVEN_OPTS="-Xms256m -Xmx512m" > Maven, adds "ms256m" and "mx512m" to the lifecycle to be executed. The output: > [DEBUG] === REACTOR BUILD PLAN > ================================================ > [DEBUG] Project: project:my-project:pom:0.0.1-SNAPSHOT > [DEBUG] Tasks: [ms256m, mx512m, clean, package] > then it fails with > [ERROR] Unknown lifecycle phase "ms256m". You must specify a valid lifecycle > phase or a goal in the format <plugin-prefi > x>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal> > -> [Help 1] > Maven should not add ms256m, mx512m as lifecycle of the project. -- 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