[
http://jira.codehaus.org/browse/MNG-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232912#action_232912
]
ccadete commented on MNG-4774:
------------------------------
I'm using cygwin to execute mvn, however, I was using mvnsh-0.10, which is
using an older version "Maven 3.0-alpha-6". When using maven-3.0-beta-2 the
problem do not occur.
> 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
>
> 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
