maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MNG-4774) Setting MAVEN_OPTS adds new lifecycles to be executed
Date Mon, 23 Aug 2010 13:37:32 GMT


Benjamin Bentmann commented on MNG-4774:

I'm not able to reproduce this (using bsh on Mac and Ubuntu) so we need some more information
about your environment. E.g. what's the output of {{echo $MAVEN_OPTS}}, what shell are you

Also, does this issue show up in 3.0-beta-2 only or also in beta-1? I wonder whether the changes
for MNG-3529 cause this.

> Setting MAVEN_OPTS adds new lifecycles to be executed
> -----------------------------------------------------
>                 Key: MNG-4774
>                 URL:
>             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:
For more information on JIRA, see:


View raw message