maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milos Kleint (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5767) project-specific default jvm options and command line parameters
Date Wed, 25 Feb 2015 22:10:18 GMT

    [ https://jira.codehaus.org/browse/MNG-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=364138#comment-364138
] 

Milos Kleint commented on MNG-5767:
-----------------------------------

how will it work for multi module projects where just a submodule is being build? will the
options be only picked up on the root project build?

> project-specific default jvm options and command line parameters
> ----------------------------------------------------------------
>
>                 Key: MNG-5767
>                 URL: https://jira.codehaus.org/browse/MNG-5767
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Igor Fedorenko
>            Assignee: Igor Fedorenko
>             Fix For: 3.2.6
>
>
> Some of the projects builds I work on require special jvm options, like minimal -Xmx
value, and specific command line parameters, like --builder. Currently, I have to manually
configure these every time run the build, which is rather annoying and error prone. This manual
configuration also makes it harder for new or external developers to build the projects and
many simply give up trying after "mvn package" does not work from the first try.
> This enhancement request proposes to introduce two new optional configuration files .mvn/jvm.config
and .mvn/maven.config, located at the base directory of project source tree. If present, these
files will provide default jvm and maven options. Because these files are part of the project
source tree, they will be present in all project checkouts and will be automatically used
every time the project is build.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message