[jira] (MNG-5767) project-specific default jvm options and command line parameters
[ https://jira.codehaus.org/browse/MNG-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=364141#comment-364141 ] Igor Fedorenko commented on MNG-5767: - Correct. Options apply for entire codebase. The same options are used regardless if the build is started at the root of the codebase or from one of the submodules. > 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)
[jira] (MNG-5767) project-specific default jvm options and command line parameters
[ 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)
[jira] (MNG-5767) project-specific default jvm options and command line parameters
[ https://jira.codehaus.org/browse/MNG-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko closed MNG-5767. --- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=8ed9a1caa8890773b45c6c408a4e40acf4f4b0fd > 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)
[jira] (MNG-5767) project-specific default jvm options and command line parameters
[ https://jira.codehaus.org/browse/MNG-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko updated MNG-5767: Fix Version/s: 3.2.6 > 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 > 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)
[jira] (MNG-5767) project-specific default jvm options and command line parameters
[ https://jira.codehaus.org/browse/MNG-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko reassigned MNG-5767: --- Assignee: Igor Fedorenko > 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)
[jira] (MNG-5767) project-specific default jvm options and command line parameters
Igor Fedorenko created MNG-5767: --- Summary: 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 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)
