Bug 1278061 - Optaplanner-examples uses same jvm instance as maven when exec plugin is used
Summary: Optaplanner-examples uses same jvm instance as maven when exec plugin is used
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: OptaPlanner
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Geoffrey De Smet
QA Contact: Jiri Locker
Depends On:
TreeView+ depends on / blocked
Reported: 2015-11-04 16:02 UTC by jvahala
Modified: 2020-03-27 19:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2020-03-27 19:10:53 UTC
Type: Bug

Attachments (Terms of Use)

Description jvahala 2015-11-04 16:02:45 UTC
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. 

Actual results:
maven should execute examples in separated JVM

Expected results:
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

Comment 2 Geoffrey De Smet 2015-11-04 16:17:03 UTC
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.

Comment 3 Geoffrey De Smet 2015-11-04 16:46:52 UTC
This issue is blocked by this upstream issue in the maven-exec-plugin:

Note You need to log in before you can comment on or make changes to this bug.