[
https://jira.codehaus.org/browse/MRELEASE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
