[jira] (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:comment-tabpanelfocusedCommentId=358809#comment-358809 ] Dan Armbrust commented on MRELEASE-206: --- I can try at some point - but I don't have an environment set up for building / testing maven tooling at the moment... will take me a bit to set things up to be able to test the patch properly. I got past my immediate issue, so I likely won't get to it real soon. I'm not entirely sure myself how the inherited vs specific options are interacting at the moment - I was hoping an expert was still hanging around getting e-mail on this thread, who could have just said yes - now that plexus-utils is much newer than it was 6 years ago... we can just add this line. I'd have to dig in and test to answer questions like that. 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)
[jira] (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:comment-tabpanelfocusedCommentId=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)
[jira] (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:comment-tabpanelfocusedCommentId=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)
[jira] (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 ] Michael Osipov updated MRELEASE-206: Fix Version/s: (was: Backlog) 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)
[jira] (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
]
Michael Osipov reopened MRELEASE-206:
-
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)
[jira] (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:comment-tabpanelfocusedCommentId=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)
[jira] (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 ] Michael Osipov closed MRELEASE-206. --- Resolution: Won't Fix Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out. 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)
