You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2022/05/06 20:57:00 UTC

[jira] [Updated] (MRELEASE-206) Pass MAVEN_OPTS to the forked release build

     [ https://issues.apache.org/jira/browse/MRELEASE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Slawomir Jaranowski updated MRELEASE-206:
-----------------------------------------
    Fix Version/s: waiting-for-feedback

> Pass MAVEN_OPTS to the forked release build
> -------------------------------------------
>
>                 Key: MRELEASE-206
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-206
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-3, 2.0-beta-4
>            Reporter: Brian E Fox
>            Priority: Major
>              Labels: contributers-welcome
>             Fix For: waiting-for-feedback
>
>
> 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
(v8.20.7#820007)