You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/07/01 14:16:43 UTC
[jira] Updated: (MRELEASE-206) its not possible to pass MAVEN_OPTS
to the forked release build
[ https://jira.codehaus.org/browse/MRELEASE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MRELEASE-206:
--------------------------------------
Fix Version/s: Backlog
Labels: contributers-welcome (was: )
Before running off and writing a patch, check back with dev@m.a.o on how you would plan to write a patch for this
> its not possible to pass MAVEN_OPTS to the forked release build
> ---------------------------------------------------------------
>
> Key: MRELEASE-206
> URL: https://jira.codehaus.org/browse/MRELEASE-206
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-3, 2.0-beta-4
> Reporter: Brian Fox
> Labels: contributers-welcome
> Fix For: Backlog
>
>
> I need to increase my jvm size for my build. The forked release doesn't get the maven_opts. I tried the -Darguments:
> mvn release:prepare -DdryRun=true -Darguments=-Xmx1024m
> gets me this:
> [INFO] Invalid task 'mx1024m': you must specify a valid lifecycle phase, or
> a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion
> :goal
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira