Officially switch from "mvn exec:exec" to "mvn exec:java" + Unrevert …

…exec-maven-plugin changes.
kiegroup · May 4, 2015 · bedf8dc · bedf8dc
1 parent 68c78df
commit bedf8dc
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 7 deletions.
diff --git a/...docs/src/main/docbook/en-US/Chapter-Planner_introduction/Chapter-Planner_introduction.xml b/...docs/src/main/docbook/en-US/Chapter-Planner_introduction/Chapter-Planner_introduction.xml
@@ -464,7 +464,7 @@ $ mvn clean install -DskipTests
           <para>Run the examples:</para>
 
           <programlisting>$ cd optaplanner-examples
-$ mvn exec:exec
+$ mvn exec:java
 ...</programlisting>
         </listitem>
 

diff --git a/optaplanner-examples/pom.xml b/optaplanner-examples/pom.xml
@@ -58,17 +58,15 @@
         <plugin>
           <groupId>org.codehaus.mojo</groupId>
           <artifactId>exec-maven-plugin</artifactId>
+          <!-- WARNING: This configuration must be run with "mvn exec:java" not "mvn exec:exec". -->
+          <!-- It is impossible to write a configuration that is compatible with both exec:java and exec:exec -->
           <configuration>
-            <executable>java</executable>
-            <classpathScope>runtime</classpathScope>
+            <mainClass>org.optaplanner.examples.app.OptaPlannerExamplesApp</mainClass>
             <arguments>
-              <!-- Most examples run (potentially slower) with max heap of 128 MB (so -Xmx128m), but 1 example's dataset requires 1.5 GB -->
               <argument>-Xms256m</argument>
+              <!-- Most examples run (potentially slower) with max heap of 128 MB (so -Xmx128m), but 1 example's dataset requires 1.5 GB -->
               <argument>-Xmx1536m</argument>
               <argument>-server</argument>
-              <argument>-cp</argument>
-              <classpath/>
-              <argument>org.optaplanner.examples.app.OptaPlannerExamplesApp</argument>
             </arguments>
           </configuration>
         </plugin>