[
https://issues.apache.org/jira/browse/MNG-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069580#comment-17069580
]
Hudson commented on MNG-5767:
-----------------------------
Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4
See
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/
> project-specific default jvm options and command line parameters
> ----------------------------------------------------------------
>
> Key: MNG-5767
> URL: https://issues.apache.org/jira/browse/MNG-5767
> Project: Maven
> Issue Type: Improvement
> Reporter: Igor Fedorenko
> Assignee: igorfie
> Priority: Major
> Fix For: 3.3.1
>
>
> 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
(v8.3.4#803005)
