Red Hat Bugzilla – Bug 1278061
Optaplanner-examples uses same jvm instance as maven when exec plugin is used
Last modified: 2016-04-28 01:08:15 EDT
Description of problem:
running optaplanner-examples in command line is done by command "mvn exec:java" right now. Problem is, that maven doesn't fork this into separated JVM instance, so examples are not executed with JVM arguments in plugin. This might cause non trivial performance issues.
maven should execute examples in separated JVM
examples are executed in default jvm for maven
how to reproduce:
1. build optaplanner-examples
2. run mvn exec:java
3. open jvisualvm and see actual java instances
From maven-exec-plugin's exec:java goal: "Note: as the execution is not forked, some system properties required by the JVM cannot be passed here. Use MAVEN_OPTS or the exec:exec instead."
For some time we used exec:exec, but for some reason we had to switch:
I've recall correctly the main reason was that users were expecting exec:java to work, and it was too much trouble to educate them to use exec:exec.
This issue is blocked by this upstream issue in the maven-exec-plugin: