Resolution: Not A Defect
Platform: All, OS: All
We have maven jobs that require specific MAVEN_OPTS to be able to complete
One example is to be able to specify the -Xmx parameter to the JVM to workaround
memory problems in the artifact deployer (which apparently pulls the whole
artifact in memory to upload it, a problem for large artifacts).
The configuration page for maven2 projects in Hudson lets you specify the
MAVEN_OPTS to use in the Advanced Build options.
One way to support support these in the m2release plugin would be to
automatically use whatever MAVEN_OPTS are specified for the job in the Advanced
Build option, if any.
Another way would be to allow us to specify the MAVEN_OPTS to use for m2release
somewhere in the configuration, either globally or per-project.