[
https://jira.codehaus.org/browse/MRELEASE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358570#comment-358570
]
Michael Osipov edited comment on MRELEASE-206 at 12/4/14 3:46 AM:
------------------------------------------------------------------
Dan, are you able to verify this with Maven 3 and provide a patch? If all
passes, I will merge.
One more question: If the system env is inherited how can you pass different
{{MAVEN_OPTS}}.
was (Author: michael-o):
Dan, are you able to verify this with Maven 3 and provide a patch. If all
passes, I will merge.
One more question: If the system env is inherited how can you pass different
{{MAVEN_OPTS}}.
> 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 Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-3, 2.0-beta-4
> Reporter: brianfox brianfox
> Labels: contributers-welcome
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
