You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/19 17:24: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 ]
Elliotte Rusty Harold updated MRELEASE-206:
-------------------------------------------
Summary: Pass MAVEN_OPTS to the forked release build (was: its not possible to pass MAVEN_OPTS to the forked release build)
> 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
>
> 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.3.4#803005)