[MINVOKER-172] Settings MAVEN_OPTS will prevent usage of invoker.mavenOpts in invoker properties

[jira-importer]

Karl Heinz Marbaise opened MINVOKER-172 and commented

If i set MAVEN_OPTS with things like export MAVEN_OPTS="-Xmx1024m -Xms1024m -Djava.awt.headless=true" in my .mavenrc it prevents the usage of invoker.mavenOpts within a invoker.properties file.

---

Affects: 1.9

Issue Links:

• MPMD-293 Fix integration test builds on jenkins

1 votes, 4 watchers

[jira-importer]

Stephan Schroevers commented

This also applies to MAVEN_OPTS set as environment variable, which is highly unintuitive. (Environment variables should override file-based settings.) Demonstration of the issue using Java 8:

$ MAVEN_OPTS="-XX:MaxPermSize=192m"
$ mvn -version | head -n 0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=192m; support was removed in 8.0 
$ echo 'MAVEN_OPTS="-XX:MaxPermSize=128m"' > ~/.mavenrc
$ mvn -version | head -n 0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.

Note that this can cause quite a bit of head scratching for Travis CI users wishing to override MAVEN_OPTS, because the build images ship with a (largely undocumented) /etc/mavenrc file. (I speak from experience...) See also Travis CI #3893.

[jira-importer]

Slawomir Jaranowski commented

I did some test and research, when /etc/mavenrc or ~/.mavenrc exist mvn script use source command and every command from mavenrc is executed before start maven.

So if in mavenrc MAVEN_OPTS is overridden we don't option to prevent this.

We can set MAVEN_SKIP_RC environment variable to skip execute commands from mavenrc

I think, that by default we should skip mavenrc - tests shouldn't depends on local environment - everything what is needed for test should be in test code.