[
https://jira.codehaus.org/browse/MRELEASE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358551#comment-358551
]
Dan Armbrust commented on MRELEASE-206:
---------------------------------------
Can we please fix this bug, now that it is 6 years old? As far as I can tell,
the very first comment contains the fix - which is a one-liner -
cli.addSystemEnvironment(); - which needs to be placed in ForkedMavenExecutor.
As far as I can tell - the concerns listed in the first comment have been
addressed years ago.
I'm running into this same issue while trying to use jgitflow - at it loses the
MAVEN_OPTS variable when it forks using the ForkedMavenExecutor - and then
fails, as my build requires more memory.
> 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
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
