3-ways-to-run-java-main-from-maven

最新推荐文章于 2021-02-16 21:47:43 发布
最新推荐文章于 2021-02-16 21:47:43 发布
阅读量2.6k 收藏
点赞数


id="twttrHubFrameSecure" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrameSecure" src="https://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;"> id="twttrHubFrame" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrame" src="http://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;">
«  Customizing Yahoo! Grids CSS, for beginners  
   How to automate project versioning and release with Maven »

3 ways to run Java main from Maven

Overview

Maven exec plugin lets you run the main method of a Java class in your project, with the project dependencies automatically included in the classpath. This article show you 3 ways of using the maven exec plugin to run java, with code examples.

1) Running from Command line

Since you are not running your code in a maven phase, you first need to compile the code. Remember exec:java does not automatically compile your code, you need to do that first.

  1. mvn compile  

Once your code is compiled, the following command runs your class

Without arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main"  
With arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.args="arg0 arg1 arg2"  
With runtime dependencies in the CLASSPATH:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.classpathScope=runtime  

2) Running in a phase in pom.xml

You can also run the main method in a maven phase. For example, you can run the CodeGenerator.main() method as part of the test phase.

view plain copy to clipboard print ?
  1. <build>  
  2.  <plugins>  
  3.   <plugin>  
  4.    <groupId>org.codehaus.mojo</groupId>  
  5.    <artifactId>exec-maven-plugin</artifactId>  
  6.    <version>1.1.1</version>  
  7.    <executions>  
  8.     <execution>  
  9.      <phase>test</phase>  
  10.      <goals>  
  11.       <goal>java</goal>  
  12.      </goals>  
  13.      <configuration>  
  14.       <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  15.       <arguments>  
  16.        <argument>arg0</argument>  
  17.        <argument>arg1</argument>  
  18.       </arguments>  
  19.      </configuration>  
  20.     </execution>  
  21.    </executions>  
  22.   </plugin>  
  23.  </plugins>  
  24. </build>  

To run the exec plugin with above configuration, simply run the corresponding phase.

  1. mvn test  

3) Running in a profile in pom.xml

You can also run the main method in a different profile. Simply wrap the above config in the <profile> tag.

view plain copy to clipboard print ?
  1. <profiles>  
  2.  <profile>  
  3.   <id>code-generator</id>  
  4.   <build>  
  5.    <plugins>  
  6.     <plugin>  
  7.      <groupId>org.codehaus.mojo</groupId>  
  8.      <artifactId>exec-maven-plugin</artifactId>  
  9.      <version>1.1.1</version>  
  10.      <executions>  
  11.       <execution>  
  12.        <phase>test</phase>  
  13.        <goals>  
  14.         <goal>java</goal>  
  15.        </goals>  
  16.        <configuration>  
  17.         <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  18.         <arguments>  
  19.          <argument>arg0</argument>  
  20.          <argument>arg1</argument>  
  21.         </arguments>  
  22.        </configuration>  
  23.       </execution>  
  24.      </executions>  
  25.     </plugin>  
  26.    </plugins>  
  27.   </build>  
  28.  </profile>  
  29. </profiles>  

To call the above profile, run the following command:

  1. mvn test -Pcode-generator  

Advanced options:

You can get a list of all available parameters by typing:

view plain copy to clipboard print ?
  1. mvn exec:help -Ddetail=true -Dgoal=java  

arguments (exec.arguments)

 The class arguments.

classpathScope (exec.classpathScope, Default: compile)

 Defines the scope of the classpath passed to the plugin. Set to
 compile, test, runtime or system depending on your needs

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
  1. [ERROR] BUILD ERROR  
  2. [INFO] ------------------------------------------------------------------------  
  3. [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:exec-maven-plugin:1.1.1  
  4. on the command line, specify: '-Dexec.arguments=VALUE'  
  5. Cause: Cannot assign configuration entry 'arguments' to 'class [Ljava.lang.String;' from '${exec.arguments}',   
  6. which is of type class java.lang.String  
  7. [INFO] ------------------------------------------------------------------------  
  8. [INFO] Trace  
  9. org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin.   
  10. Reason: Unable to parse the created DOM for plugin configuration  
  11.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:588)  
  12.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)  
  13.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)  
  14.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)  
  15.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)  
  16.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)  
  17.  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)  
  18.  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)  
  19.  at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)  

Solution

exec.arguments was used before version 1.1 of the exec plugin, it did not support conversion of command line String to String[] array.

  1. If possible upgrade to 1.1 or later and use exec.args instead of exec.arguments.
  2. If you can't upgrade the plugin version, you can still use command line arguments with a profile and use multiple <argument> tags associated in the pom.xml

References

    

name="f12f15e27c" width="1000px" height="1000px" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" title="fb:like Facebook Social Plugin" src="http://www.facebook.com/plugins/like.php?app_id=&channel=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter%2F6brUqVNoWO3.js%3Fversion%3D41%23cb%3Df2e7c6ef94%26domain%3Dwww.vineetmanohar.com%26origin%3Dhttp%253A%252F%252Fwww.vineetmanohar.com%252Ff26632479%26relation%3Dparent.parent&container_width=0&href=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&layout=button_count&locale=en_US&sdk=joey&send=false&show_faces=false" style="position: absolute; border-style: none; visibility: visible; width: 78px; height: 20px;">
 
frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" tabindex="0" vspace="0" width="100%" id="I0_1443515785671" name="I0_1443515785671" src="https://apis.google.com/se/0/_/+1/fastbutton?usegapi=1&size=medium&count=false&origin=http%3A%2F%2Fwww.vineetmanohar.com&url=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&gsrc=3p&ic=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.vi.5hpnngUu-2A.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCPTSqOYkaP1U6q4oCWtRMtgv6oPUA#_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart%2Concircled%2Cdrefresh%2Cerefresh&id=I0_1443515785671&parent=http%3A%2F%2Fwww.vineetmanohar.com&pfname=&rpctoken=42774078" data-gapiattached="true" title="+1" style="position: static; top: 0px; width: 32px; margin: 0px; border-style: none; left: 0px; visibility: visible; height: 20px;">

Related posts:

  1. The plugin ‘org.codehaus.mojo:selenium-maven-plugin’ does not exist or no valid version could be found
  2. Tweet your builds with Maven Twitter Plugin
  3. How to automate project versioning and release with Maven
  4. JAXB code snippets for beginners
  5. How to display maven project version in your webapp
November 2nd, 2009 | Tags:  java,  maven,  maven exec plugin,  maven java,  maven plugin,  mvn,  pom.xml | Category:  java,  Tech |  21 comments

21 comments to 3 ways to run Java main from Maven

  • Erik
    November 4th, 2009 at 6:45 am

    Don’t forget the Maven CLI method, it’s waaay faster than anything else!

  • vineet
    December 9th, 2009 at 2:33 am

    If you get the following error:
    Project ID: org.codehaus.mojo:maven-exec-plugin
    POM Location: ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom
    Reason: Not a v4.0.0 POM. for project org.codehaus.mojo:maven-exec-plugin at ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom

    and the following content in the file: ~/.m2/repository/org/apache/maven/plugins/maven-exec-plugin/maven-metadata-java.net.xml


    < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Moved Permanently

    The document has moved here.

    Apache Server at maven-repository.dev.java.net Port 443


    Try the full command line:
    mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

  • Kamal
    June 16th, 2010 at 3:26 pm

    Thanks folks. I am using the maven-exec plugin to run jarsigner and get surprised by the following:
    jarsigner ${project.build.directory}\jarname bla bla bla

    However, assume the value of ${project.build.directory} is C:\somedir\somesubdir, the exec is ripping off all the slashes in the build directory path and tries to pass”

    C:somedirsomeubdir

    Any ideas?
    Thanks a log

  • flurdy
    July 8th, 2010 at 8:33 am

    @Kamal try forwards slashes instead of backslashes

  • Tim
    August 30th, 2010 at 11:15 am

    So how would I java my -javaagent= arg.. exec.args gives it to the class being run…

  • Tim
    August 30th, 2010 at 11:20 am

    Oh I see now. Run export MAVEN_OPTS=-javaagent:.. first.

  • Jesse Glick
    February 16th, 2011 at 7:23 pm

    Consider using exec:exec rather than exec:java for running your own project, unless the code in question is really a bit of build tool. Discussed here: http://maven.40175.n5.nabble.com/Call-System-setProperty-quot-java-awt-headless-quot-true-td3383750.html#a3388567

    (Hi Vineet!)

  • norman rm
    March 15th, 2011 at 6:57 pm

    thanks

  • Max Mohave
    March 17th, 2011 at 10:59 pm

    Dear Vineet:

    thank, I used your info to run my new application by MVN command line. Do you use an IDE with MAVEN to run and if so which one. And lastly, can you tell me how you would use the equivalent of mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

    to run in that IDE?

    Thanks so much.

  • vineet
    March 18th, 2011 at 4:22 pm

    I use Eclipse. I first run “mvn eclipse:eclipse” to export the project into eclipse format. Then import the project by using File -> Import -> Import existing project.

    However, I use mvn from command line and not from inside the IDE.

    There are eclipse plugins for maven (like m2eclipse) that you can use from inside Eclipse but I don’t use them.

  • Max Mohave
    March 18th, 2011 at 6:55 pm

    Thank you. I appreciate your skill and time.
    Sincerely, Max

  • Finn
    April 27th, 2011 at 6:26 am

    Highest quality blog post ever, exactly what I needed. Thank you.

  • Terence
    November 3rd, 2011 at 11:46 pm

    Thanks. Combined with your post and the maven doco, it took me about 10 minutes to have it working and documented.

  • Akilan
    November 30th, 2011 at 10:37 am

    Thanks Vineet. Wonderful blog and exactly what I searched for.

  • Anil Kesariya
    February 2nd, 2012 at 1:42 am

    hello i m anil

    i m first time working with maven.. so i dont that how should we work with it , i got lession that how we can generate jar file from our java file using maven
    so please tell me that how should i work with it..i have only one day dead line..

  • Tensy
    February 2nd, 2012 at 3:29 pm

    Hi Vineet, This post is really useful.
    However, when I try to run the command, I see the following.
    Command: mvn org.codehaus.mojo:exec-maven-plugin:1.2:java -e -Dexec.mainClass=com.myclass.Wsdl2XsdConverter

    An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. com.qpass.googlecarrierbilling.Wsdl2XsdConverter
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    … 16 more
    Caused by: java.lang.ClassNotFoundException: com.myclass.Wsdl2XsdConverter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:284)
    at java.lang.Thread.run(Thread.java:595)

    I run the mvn compile command also prior to running the above mentioned mvn command.
    Any help is greatly appreciated.

  • vineet
    February 2nd, 2012 at 4:38 pm

    Looks right to me.

    I would try the following:
    1) Try mvn -X to generate more debug info.
    2) Also try the other approach as described in section 2) above: “Running in a phase in pom.xml”, see if that works.

  • Ramaraj
    February 27th, 2012 at 8:06 am

    Thank you for your time and effort to create this blog. I have got more info than what i need.

  • andres
    March 1st, 2012 at 5:16 am

    Thanks a lot. but how to package all depedencies into single jar

  • Dev
    April 9th, 2012 at 10:35 am

    Content is very helpful.
    Please tell me how can i debug while executing my main class. I used Eclipse.

    Thanks

  • Yashaswini
    April 25th, 2012 at 2:30 am

    Hi,
    I need to trigger a makefile through Maven. Could someone please tell how this can be done? Can exec-maven-plugin be used to execute a makefile? When I use exec-maven-plugin to execute my makefile, I get the following error:
    [INFO] — exec-maven-plugin:1.1:exec (buildlib) @ nativeTestProjectMaven —
    [INFO] ‘”C:\Program Files\apache-maven-3.0.4\TestProjectMaven\src\main\native\ma
    kefile”‘ is not recognized as an internal or external command,
    [INFO] operable program or batch file.

Leave a Reply

  

  

  

You can use these HTML tags

name="fb_xdm_frame_http" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_http" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="http://static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;"> name="fb_xdm_frame_https" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_https" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="https://s-static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;">
name="oauth2relay651382484" id="oauth2relay651382484" src="https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.vineetmanohar.com#rpctoken=784954501&forcesecure=1" tabindex="-1" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; width: 1px; height: 1px; position: absolute; top: -100px;">
ShareThis Copy and Paste
- See more at: http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/#sthash.T70JUj6V.dpuf id="twttrHubFrameSecure" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrameSecure" src="https://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;"> id="twttrHubFrame" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrame" src="http://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;">
«  Customizing Yahoo! Grids CSS, for beginners  
   How to automate project versioning and release with Maven »

3 ways to run Java main from Maven

Overview

Maven exec plugin lets you run the main method of a Java class in your project, with the project dependencies automatically included in the classpath. This article show you 3 ways of using the maven exec plugin to run java, with code examples.

1) Running from Command line

Since you are not running your code in a maven phase, you first need to compile the code. Remember exec:java does not automatically compile your code, you need to do that first.

  1. mvn compile  

Once your code is compiled, the following command runs your class

Without arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main"  
With arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.args="arg0 arg1 arg2"  
With runtime dependencies in the CLASSPATH:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.classpathScope=runtime  

2) Running in a phase in pom.xml

You can also run the main method in a maven phase. For example, you can run the CodeGenerator.main() method as part of the test phase.

view plain copy to clipboard print ?
  1. <build>  
  2.  <plugins>  
  3.   <plugin>  
  4.    <groupId>org.codehaus.mojo</groupId>  
  5.    <artifactId>exec-maven-plugin</artifactId>  
  6.    <version>1.1.1</version>  
  7.    <executions>  
  8.     <execution>  
  9.      <phase>test</phase>  
  10.      <goals>  
  11.       <goal>java</goal>  
  12.      </goals>  
  13.      <configuration>  
  14.       <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  15.       <arguments>  
  16.        <argument>arg0</argument>  
  17.        <argument>arg1</argument>  
  18.       </arguments>  
  19.      </configuration>  
  20.     </execution>  
  21.    </executions>  
  22.   </plugin>  
  23.  </plugins>  
  24. </build>  

To run the exec plugin with above configuration, simply run the corresponding phase.

  1. mvn test  

3) Running in a profile in pom.xml

You can also run the main method in a different profile. Simply wrap the above config in the <profile> tag.

view plain copy to clipboard print ?
  1. <profiles>  
  2.  <profile>  
  3.   <id>code-generator</id>  
  4.   <build>  
  5.    <plugins>  
  6.     <plugin>  
  7.      <groupId>org.codehaus.mojo</groupId>  
  8.      <artifactId>exec-maven-plugin</artifactId>  
  9.      <version>1.1.1</version>  
  10.      <executions>  
  11.       <execution>  
  12.        <phase>test</phase>  
  13.        <goals>  
  14.         <goal>java</goal>  
  15.        </goals>  
  16.        <configuration>  
  17.         <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  18.         <arguments>  
  19.          <argument>arg0</argument>  
  20.          <argument>arg1</argument>  
  21.         </arguments>  
  22.        </configuration>  
  23.       </execution>  
  24.      </executions>  
  25.     </plugin>  
  26.    </plugins>  
  27.   </build>  
  28.  </profile>  
  29. </profiles>  

To call the above profile, run the following command:

  1. mvn test -Pcode-generator  

Advanced options:

You can get a list of all available parameters by typing:

view plain copy to clipboard print ?
  1. mvn exec:help -Ddetail=true -Dgoal=java  

arguments (exec.arguments)

 The class arguments.

classpathScope (exec.classpathScope, Default: compile)

 Defines the scope of the classpath passed to the plugin. Set to
 compile, test, runtime or system depending on your needs

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
  1. [ERROR] BUILD ERROR  
  2. [INFO] ------------------------------------------------------------------------  
  3. [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:exec-maven-plugin:1.1.1  
  4. on the command line, specify: '-Dexec.arguments=VALUE'  
  5. Cause: Cannot assign configuration entry 'arguments' to 'class [Ljava.lang.String;' from '${exec.arguments}',   
  6. which is of type class java.lang.String  
  7. [INFO] ------------------------------------------------------------------------  
  8. [INFO] Trace  
  9. org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin.   
  10. Reason: Unable to parse the created DOM for plugin configuration  
  11.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:588)  
  12.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)  
  13.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)  
  14.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)  
  15.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)  
  16.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)  
  17.  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)  
  18.  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)  
  19.  at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)  

Solution

exec.arguments was used before version 1.1 of the exec plugin, it did not support conversion of command line String to String[] array.

  1. If possible upgrade to 1.1 or later and use exec.args instead of exec.arguments.
  2. If you can't upgrade the plugin version, you can still use command line arguments with a profile and use multiple <argument> tags associated in the pom.xml

References

    

name="f12f15e27c" width="1000px" height="1000px" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" title="fb:like Facebook Social Plugin" src="http://www.facebook.com/plugins/like.php?app_id=&channel=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter%2F6brUqVNoWO3.js%3Fversion%3D41%23cb%3Df2e7c6ef94%26domain%3Dwww.vineetmanohar.com%26origin%3Dhttp%253A%252F%252Fwww.vineetmanohar.com%252Ff26632479%26relation%3Dparent.parent&container_width=0&href=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&layout=button_count&locale=en_US&sdk=joey&send=false&show_faces=false" style="position: absolute; border-style: none; visibility: visible; width: 78px; height: 20px;">
 
frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" tabindex="0" vspace="0" width="100%" id="I0_1443515785671" name="I0_1443515785671" src="https://apis.google.com/se/0/_/+1/fastbutton?usegapi=1&size=medium&count=false&origin=http%3A%2F%2Fwww.vineetmanohar.com&url=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&gsrc=3p&ic=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.vi.5hpnngUu-2A.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCPTSqOYkaP1U6q4oCWtRMtgv6oPUA#_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart%2Concircled%2Cdrefresh%2Cerefresh&id=I0_1443515785671&parent=http%3A%2F%2Fwww.vineetmanohar.com&pfname=&rpctoken=42774078" data-gapiattached="true" title="+1" style="position: static; top: 0px; width: 32px; margin: 0px; border-style: none; left: 0px; visibility: visible; height: 20px;">

Related posts:

  1. The plugin ‘org.codehaus.mojo:selenium-maven-plugin’ does not exist or no valid version could be found
  2. Tweet your builds with Maven Twitter Plugin
  3. How to automate project versioning and release with Maven
  4. JAXB code snippets for beginners
  5. How to display maven project version in your webapp
November 2nd, 2009 | Tags:  java,  maven,  maven exec plugin,  maven java,  maven plugin,  mvn,  pom.xml | Category:  java,  Tech |  21 comments

21 comments to 3 ways to run Java main from Maven

  • Erik
    November 4th, 2009 at 6:45 am

    Don’t forget the Maven CLI method, it’s waaay faster than anything else!

  • vineet
    December 9th, 2009 at 2:33 am

    If you get the following error:
    Project ID: org.codehaus.mojo:maven-exec-plugin
    POM Location: ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom
    Reason: Not a v4.0.0 POM. for project org.codehaus.mojo:maven-exec-plugin at ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom

    and the following content in the file: ~/.m2/repository/org/apache/maven/plugins/maven-exec-plugin/maven-metadata-java.net.xml


    < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Moved Permanently

    The document has moved here.

    Apache Server at maven-repository.dev.java.net Port 443


    Try the full command line:
    mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

  • Kamal
    June 16th, 2010 at 3:26 pm

    Thanks folks. I am using the maven-exec plugin to run jarsigner and get surprised by the following:
    jarsigner ${project.build.directory}\jarname bla bla bla

    However, assume the value of ${project.build.directory} is C:\somedir\somesubdir, the exec is ripping off all the slashes in the build directory path and tries to pass”

    C:somedirsomeubdir

    Any ideas?
    Thanks a log

  • flurdy
    July 8th, 2010 at 8:33 am

    @Kamal try forwards slashes instead of backslashes

  • Tim
    August 30th, 2010 at 11:15 am

    So how would I java my -javaagent= arg.. exec.args gives it to the class being run…

  • Tim
    August 30th, 2010 at 11:20 am

    Oh I see now. Run export MAVEN_OPTS=-javaagent:.. first.

  • Jesse Glick
    February 16th, 2011 at 7:23 pm

    Consider using exec:exec rather than exec:java for running your own project, unless the code in question is really a bit of build tool. Discussed here: http://maven.40175.n5.nabble.com/Call-System-setProperty-quot-java-awt-headless-quot-true-td3383750.html#a3388567

    (Hi Vineet!)

  • norman rm
    March 15th, 2011 at 6:57 pm

    thanks

  • Max Mohave
    March 17th, 2011 at 10:59 pm

    Dear Vineet:

    thank, I used your info to run my new application by MVN command line. Do you use an IDE with MAVEN to run and if so which one. And lastly, can you tell me how you would use the equivalent of mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

    to run in that IDE?

    Thanks so much.

  • vineet
    March 18th, 2011 at 4:22 pm

    I use Eclipse. I first run “mvn eclipse:eclipse” to export the project into eclipse format. Then import the project by using File -> Import -> Import existing project.

    However, I use mvn from command line and not from inside the IDE.

    There are eclipse plugins for maven (like m2eclipse) that you can use from inside Eclipse but I don’t use them.

  • Max Mohave
    March 18th, 2011 at 6:55 pm

    Thank you. I appreciate your skill and time.
    Sincerely, Max

  • Finn
    April 27th, 2011 at 6:26 am

    Highest quality blog post ever, exactly what I needed. Thank you.

  • Terence
    November 3rd, 2011 at 11:46 pm

    Thanks. Combined with your post and the maven doco, it took me about 10 minutes to have it working and documented.

  • Akilan
    November 30th, 2011 at 10:37 am

    Thanks Vineet. Wonderful blog and exactly what I searched for.

  • Anil Kesariya
    February 2nd, 2012 at 1:42 am

    hello i m anil

    i m first time working with maven.. so i dont that how should we work with it , i got lession that how we can generate jar file from our java file using maven
    so please tell me that how should i work with it..i have only one day dead line..

  • Tensy
    February 2nd, 2012 at 3:29 pm

    Hi Vineet, This post is really useful.
    However, when I try to run the command, I see the following.
    Command: mvn org.codehaus.mojo:exec-maven-plugin:1.2:java -e -Dexec.mainClass=com.myclass.Wsdl2XsdConverter

    An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. com.qpass.googlecarrierbilling.Wsdl2XsdConverter
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    … 16 more
    Caused by: java.lang.ClassNotFoundException: com.myclass.Wsdl2XsdConverter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:284)
    at java.lang.Thread.run(Thread.java:595)

    I run the mvn compile command also prior to running the above mentioned mvn command.
    Any help is greatly appreciated.

  • vineet
    February 2nd, 2012 at 4:38 pm

    Looks right to me.

    I would try the following:
    1) Try mvn -X to generate more debug info.
    2) Also try the other approach as described in section 2) above: “Running in a phase in pom.xml”, see if that works.

  • Ramaraj
    February 27th, 2012 at 8:06 am

    Thank you for your time and effort to create this blog. I have got more info than what i need.

  • andres
    March 1st, 2012 at 5:16 am

    Thanks a lot. but how to package all depedencies into single jar

  • Dev
    April 9th, 2012 at 10:35 am

    Content is very helpful.
    Please tell me how can i debug while executing my main class. I used Eclipse.

    Thanks

  • Yashaswini
    April 25th, 2012 at 2:30 am

    Hi,
    I need to trigger a makefile through Maven. Could someone please tell how this can be done? Can exec-maven-plugin be used to execute a makefile? When I use exec-maven-plugin to execute my makefile, I get the following error:
    [INFO] — exec-maven-plugin:1.1:exec (buildlib) @ nativeTestProjectMaven —
    [INFO] ‘”C:\Program Files\apache-maven-3.0.4\TestProjectMaven\src\main\native\ma
    kefile”‘ is not recognized as an internal or external command,
    [INFO] operable program or batch file.

Leave a Reply

  

  

  

You can use these HTML tags

name="fb_xdm_frame_http" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_http" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="http://static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;"> name="fb_xdm_frame_https" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_https" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="https://s-static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;">
name="oauth2relay651382484" id="oauth2relay651382484" src="https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.vineetmanohar.com#rpctoken=784954501&forcesecure=1" tabindex="-1" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; width: 1px; height: 1px; position: absolute; top: -100px;">
ShareThis Copy and Paste
- See more at: http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/#sthash.T70JUj6V.dpuf


cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?


id="twttrHubFrameSecure" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrameSecure" src="https://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;"> id="twttrHubFrame" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrame" src="http://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;">
«  Customizing Yahoo! Grids CSS, for beginners  
   How to automate project versioning and release with Maven »

3 ways to run Java main from Maven

Overview

Maven exec plugin lets you run the main method of a Java class in your project, with the project dependencies automatically included in the classpath. This article show you 3 ways of using the maven exec plugin to run java, with code examples.

1) Running from Command line

Since you are not running your code in a maven phase, you first need to compile the code. Remember exec:java does not automatically compile your code, you need to do that first.

  1. mvn compile  

Once your code is compiled, the following command runs your class

Without arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main"  
With arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.args="arg0 arg1 arg2"  
With runtime dependencies in the CLASSPATH:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.classpathScope=runtime  

2) Running in a phase in pom.xml

You can also run the main method in a maven phase. For example, you can run the CodeGenerator.main() method as part of the test phase.

view plain copy to clipboard print ?
  1. <build>  
  2.  <plugins>  
  3.   <plugin>  
  4.    <groupId>org.codehaus.mojo</groupId>  
  5.    <artifactId>exec-maven-plugin</artifactId>  
  6.    <version>1.1.1</version>  
  7.    <executions>  
  8.     <execution>  
  9.      <phase>test</phase>  
  10.      <goals>  
  11.       <goal>java</goal>  
  12.      </goals>  
  13.      <configuration>  
  14.       <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  15.       <arguments>  
  16.        <argument>arg0</argument>  
  17.        <argument>arg1</argument>  
  18.       </arguments>  
  19.      </configuration>  
  20.     </execution>  
  21.    </executions>  
  22.   </plugin>  
  23.  </plugins>  
  24. </build>  

To run the exec plugin with above configuration, simply run the corresponding phase.

  1. mvn test  

3) Running in a profile in pom.xml

You can also run the main method in a different profile. Simply wrap the above config in the <profile> tag.

view plain copy to clipboard print ?
  1. <profiles>  
  2.  <profile>  
  3.   <id>code-generator</id>  
  4.   <build>  
  5.    <plugins>  
  6.     <plugin>  
  7.      <groupId>org.codehaus.mojo</groupId>  
  8.      <artifactId>exec-maven-plugin</artifactId>  
  9.      <version>1.1.1</version>  
  10.      <executions>  
  11.       <execution>  
  12.        <phase>test</phase>  
  13.        <goals>  
  14.         <goal>java</goal>  
  15.        </goals>  
  16.        <configuration>  
  17.         <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  18.         <arguments>  
  19.          <argument>arg0</argument>  
  20.          <argument>arg1</argument>  
  21.         </arguments>  
  22.        </configuration>  
  23.       </execution>  
  24.      </executions>  
  25.     </plugin>  
  26.    </plugins>  
  27.   </build>  
  28.  </profile>  
  29. </profiles>  

To call the above profile, run the following command:

  1. mvn test -Pcode-generator  

Advanced options:

You can get a list of all available parameters by typing:

view plain copy to clipboard print ?
  1. mvn exec:help -Ddetail=true -Dgoal=java  

arguments (exec.arguments)

 The class arguments.

classpathScope (exec.classpathScope, Default: compile)

 Defines the scope of the classpath passed to the plugin. Set to
 compile, test, runtime or system depending on your needs

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
  1. [ERROR] BUILD ERROR  
  2. [INFO] ------------------------------------------------------------------------  
  3. [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:exec-maven-plugin:1.1.1  
  4. on the command line, specify: '-Dexec.arguments=VALUE'  
  5. Cause: Cannot assign configuration entry 'arguments' to 'class [Ljava.lang.String;' from '${exec.arguments}',   
  6. which is of type class java.lang.String  
  7. [INFO] ------------------------------------------------------------------------  
  8. [INFO] Trace  
  9. org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin.   
  10. Reason: Unable to parse the created DOM for plugin configuration  
  11.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:588)  
  12.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)  
  13.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)  
  14.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)  
  15.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)  
  16.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)  
  17.  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)  
  18.  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)  
  19.  at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)  

Solution

exec.arguments was used before version 1.1 of the exec plugin, it did not support conversion of command line String to String[] array.

  1. If possible upgrade to 1.1 or later and use exec.args instead of exec.arguments.
  2. If you can't upgrade the plugin version, you can still use command line arguments with a profile and use multiple <argument> tags associated in the pom.xml

References

    

name="f12f15e27c" width="1000px" height="1000px" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" title="fb:like Facebook Social Plugin" src="http://www.facebook.com/plugins/like.php?app_id=&channel=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter%2F6brUqVNoWO3.js%3Fversion%3D41%23cb%3Df2e7c6ef94%26domain%3Dwww.vineetmanohar.com%26origin%3Dhttp%253A%252F%252Fwww.vineetmanohar.com%252Ff26632479%26relation%3Dparent.parent&container_width=0&href=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&layout=button_count&locale=en_US&sdk=joey&send=false&show_faces=false" style="position: absolute; border-style: none; visibility: visible; width: 78px; height: 20px;">
 
frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" tabindex="0" vspace="0" width="100%" id="I0_1443515785671" name="I0_1443515785671" src="https://apis.google.com/se/0/_/+1/fastbutton?usegapi=1&size=medium&count=false&origin=http%3A%2F%2Fwww.vineetmanohar.com&url=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&gsrc=3p&ic=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.vi.5hpnngUu-2A.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCPTSqOYkaP1U6q4oCWtRMtgv6oPUA#_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart%2Concircled%2Cdrefresh%2Cerefresh&id=I0_1443515785671&parent=http%3A%2F%2Fwww.vineetmanohar.com&pfname=&rpctoken=42774078" data-gapiattached="true" title="+1" style="position: static; top: 0px; width: 32px; margin: 0px; border-style: none; left: 0px; visibility: visible; height: 20px;">

Related posts:

  1. The plugin ‘org.codehaus.mojo:selenium-maven-plugin’ does not exist or no valid version could be found
  2. Tweet your builds with Maven Twitter Plugin
  3. How to automate project versioning and release with Maven
  4. JAXB code snippets for beginners
  5. How to display maven project version in your webapp
November 2nd, 2009 | Tags:  java,  maven,  maven exec plugin,  maven java,  maven plugin,  mvn,  pom.xml | Category:  java,  Tech |  21 comments

21 comments to 3 ways to run Java main from Maven

  • Erik
    November 4th, 2009 at 6:45 am

    Don’t forget the Maven CLI method, it’s waaay faster than anything else!

  • vineet
    December 9th, 2009 at 2:33 am

    If you get the following error:
    Project ID: org.codehaus.mojo:maven-exec-plugin
    POM Location: ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom
    Reason: Not a v4.0.0 POM. for project org.codehaus.mojo:maven-exec-plugin at ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom

    and the following content in the file: ~/.m2/repository/org/apache/maven/plugins/maven-exec-plugin/maven-metadata-java.net.xml


    < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Moved Permanently

    The document has moved here.

    Apache Server at maven-repository.dev.java.net Port 443


    Try the full command line:
    mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

  • Kamal
    June 16th, 2010 at 3:26 pm

    Thanks folks. I am using the maven-exec plugin to run jarsigner and get surprised by the following:
    jarsigner ${project.build.directory}\jarname bla bla bla

    However, assume the value of ${project.build.directory} is C:\somedir\somesubdir, the exec is ripping off all the slashes in the build directory path and tries to pass”

    C:somedirsomeubdir

    Any ideas?
    Thanks a log

  • flurdy
    July 8th, 2010 at 8:33 am

    @Kamal try forwards slashes instead of backslashes

  • Tim
    August 30th, 2010 at 11:15 am

    So how would I java my -javaagent= arg.. exec.args gives it to the class being run…

  • Tim
    August 30th, 2010 at 11:20 am

    Oh I see now. Run export MAVEN_OPTS=-javaagent:.. first.

  • Jesse Glick
    February 16th, 2011 at 7:23 pm

    Consider using exec:exec rather than exec:java for running your own project, unless the code in question is really a bit of build tool. Discussed here: http://maven.40175.n5.nabble.com/Call-System-setProperty-quot-java-awt-headless-quot-true-td3383750.html#a3388567

    (Hi Vineet!)

  • norman rm
    March 15th, 2011 at 6:57 pm

    thanks

  • Max Mohave
    March 17th, 2011 at 10:59 pm

    Dear Vineet:

    thank, I used your info to run my new application by MVN command line. Do you use an IDE with MAVEN to run and if so which one. And lastly, can you tell me how you would use the equivalent of mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

    to run in that IDE?

    Thanks so much.

  • vineet
    March 18th, 2011 at 4:22 pm

    I use Eclipse. I first run “mvn eclipse:eclipse” to export the project into eclipse format. Then import the project by using File -> Import -> Import existing project.

    However, I use mvn from command line and not from inside the IDE.

    There are eclipse plugins for maven (like m2eclipse) that you can use from inside Eclipse but I don’t use them.

  • Max Mohave
    March 18th, 2011 at 6:55 pm

    Thank you. I appreciate your skill and time.
    Sincerely, Max

  • Finn
    April 27th, 2011 at 6:26 am

    Highest quality blog post ever, exactly what I needed. Thank you.

  • Terence
    November 3rd, 2011 at 11:46 pm

    Thanks. Combined with your post and the maven doco, it took me about 10 minutes to have it working and documented.

  • Akilan
    November 30th, 2011 at 10:37 am

    Thanks Vineet. Wonderful blog and exactly what I searched for.

  • Anil Kesariya
    February 2nd, 2012 at 1:42 am

    hello i m anil

    i m first time working with maven.. so i dont that how should we work with it , i got lession that how we can generate jar file from our java file using maven
    so please tell me that how should i work with it..i have only one day dead line..

  • Tensy
    February 2nd, 2012 at 3:29 pm

    Hi Vineet, This post is really useful.
    However, when I try to run the command, I see the following.
    Command: mvn org.codehaus.mojo:exec-maven-plugin:1.2:java -e -Dexec.mainClass=com.myclass.Wsdl2XsdConverter

    An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. com.qpass.googlecarrierbilling.Wsdl2XsdConverter
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    … 16 more
    Caused by: java.lang.ClassNotFoundException: com.myclass.Wsdl2XsdConverter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:284)
    at java.lang.Thread.run(Thread.java:595)

    I run the mvn compile command also prior to running the above mentioned mvn command.
    Any help is greatly appreciated.

  • vineet
    February 2nd, 2012 at 4:38 pm

    Looks right to me.

    I would try the following:
    1) Try mvn -X to generate more debug info.
    2) Also try the other approach as described in section 2) above: “Running in a phase in pom.xml”, see if that works.

  • Ramaraj
    February 27th, 2012 at 8:06 am

    Thank you for your time and effort to create this blog. I have got more info than what i need.

  • andres
    March 1st, 2012 at 5:16 am

    Thanks a lot. but how to package all depedencies into single jar

  • Dev
    April 9th, 2012 at 10:35 am

    Content is very helpful.
    Please tell me how can i debug while executing my main class. I used Eclipse.

    Thanks

  • Yashaswini
    April 25th, 2012 at 2:30 am

    Hi,
    I need to trigger a makefile through Maven. Could someone please tell how this can be done? Can exec-maven-plugin be used to execute a makefile? When I use exec-maven-plugin to execute my makefile, I get the following error:
    [INFO] — exec-maven-plugin:1.1:exec (buildlib) @ nativeTestProjectMaven —
    [INFO] ‘”C:\Program Files\apache-maven-3.0.4\TestProjectMaven\src\main\native\ma
    kefile”‘ is not recognized as an internal or external command,
    [INFO] operable program or batch file.

Leave a Reply

  

  

  

You can use these HTML tags

name="fb_xdm_frame_http" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_http" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="http://static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;"> name="fb_xdm_frame_https" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_https" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="https://s-static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;">
name="oauth2relay651382484" id="oauth2relay651382484" src="https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.vineetmanohar.com#rpctoken=784954501&forcesecure=1" tabindex="-1" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; width: 1px; height: 1px; position: absolute; top: -100px;">
ShareThis Copy and Paste
- See more at: http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/#sthash.T70JUj6V.dpuf id="twttrHubFrameSecure" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrameSecure" src="https://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;"> id="twttrHubFrame" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrame" src="http://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;">
«  Customizing Yahoo! Grids CSS, for beginners  
   How to automate project versioning and release with Maven »

3 ways to run Java main from Maven

Overview

Maven exec plugin lets you run the main method of a Java class in your project, with the project dependencies automatically included in the classpath. This article show you 3 ways of using the maven exec plugin to run java, with code examples.

1) Running from Command line

Since you are not running your code in a maven phase, you first need to compile the code. Remember exec:java does not automatically compile your code, you need to do that first.

  1. mvn compile  

Once your code is compiled, the following command runs your class

Without arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main"  
With arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.args="arg0 arg1 arg2"  
With runtime dependencies in the CLASSPATH:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.classpathScope=runtime  

2) Running in a phase in pom.xml

You can also run the main method in a maven phase. For example, you can run the CodeGenerator.main() method as part of the test phase.

view plain copy to clipboard print ?
  1. <build>  
  2.  <plugins>  
  3.   <plugin>  
  4.    <groupId>org.codehaus.mojo</groupId>  
  5.    <artifactId>exec-maven-plugin</artifactId>  
  6.    <version>1.1.1</version>  
  7.    <executions>  
  8.     <execution>  
  9.      <phase>test</phase>  
  10.      <goals>  
  11.       <goal>java</goal>  
  12.      </goals>  
  13.      <configuration>  
  14.       <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  15.       <arguments>  
  16.        <argument>arg0</argument>  
  17.        <argument>arg1</argument>  
  18.       </arguments>  
  19.      </configuration>  
  20.     </execution>  
  21.    </executions>  
  22.   </plugin>  
  23.  </plugins>  
  24. </build>  

To run the exec plugin with above configuration, simply run the corresponding phase.

  1. mvn test  

3) Running in a profile in pom.xml

You can also run the main method in a different profile. Simply wrap the above config in the <profile> tag.

view plain copy to clipboard print ?
  1. <profiles>  
  2.  <profile>  
  3.   <id>code-generator</id>  
  4.   <build>  
  5.    <plugins>  
  6.     <plugin>  
  7.      <groupId>org.codehaus.mojo</groupId>  
  8.      <artifactId>exec-maven-plugin</artifactId>  
  9.      <version>1.1.1</version>  
  10.      <executions>  
  11.       <execution>  
  12.        <phase>test</phase>  
  13.        <goals>  
  14.         <goal>java</goal>  
  15.        </goals>  
  16.        <configuration>  
  17.         <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  18.         <arguments>  
  19.          <argument>arg0</argument>  
  20.          <argument>arg1</argument>  
  21.         </arguments>  
  22.        </configuration>  
  23.       </execution>  
  24.      </executions>  
  25.     </plugin>  
  26.    </plugins>  
  27.   </build>  
  28.  </profile>  
  29. </profiles>  

To call the above profile, run the following command:

  1. mvn test -Pcode-generator  

Advanced options:

You can get a list of all available parameters by typing:

view plain copy to clipboard print ?
  1. mvn exec:help -Ddetail=true -Dgoal=java  

arguments (exec.arguments)

 The class arguments.

classpathScope (exec.classpathScope, Default: compile)

 Defines the scope of the classpath passed to the plugin. Set to
 compile, test, runtime or system depending on your needs

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
  1. [ERROR] BUILD ERROR  
  2. [INFO] ------------------------------------------------------------------------  
  3. [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:exec-maven-plugin:1.1.1  
  4. on the command line, specify: '-Dexec.arguments=VALUE'  
  5. Cause: Cannot assign configuration entry 'arguments' to 'class [Ljava.lang.String;' from '${exec.arguments}',   
  6. which is of type class java.lang.String  
  7. [INFO] ------------------------------------------------------------------------  
  8. [INFO] Trace  
  9. org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin.   
  10. Reason: Unable to parse the created DOM for plugin configuration  
  11.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:588)  
  12.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)  
  13.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)  
  14.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)  
  15.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)  
  16.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)  
  17.  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)  
  18.  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)  
  19.  at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)  

Solution

exec.arguments was used before version 1.1 of the exec plugin, it did not support conversion of command line String to String[] array.

  1. If possible upgrade to 1.1 or later and use exec.args instead of exec.arguments.
  2. If you can't upgrade the plugin version, you can still use command line arguments with a profile and use multiple <argument> tags associated in the pom.xml

References

    

name="f12f15e27c" width="1000px" height="1000px" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" title="fb:like Facebook Social Plugin" src="http://www.facebook.com/plugins/like.php?app_id=&channel=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter%2F6brUqVNoWO3.js%3Fversion%3D41%23cb%3Df2e7c6ef94%26domain%3Dwww.vineetmanohar.com%26origin%3Dhttp%253A%252F%252Fwww.vineetmanohar.com%252Ff26632479%26relation%3Dparent.parent&container_width=0&href=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&layout=button_count&locale=en_US&sdk=joey&send=false&show_faces=false" style="position: absolute; border-style: none; visibility: visible; width: 78px; height: 20px;">
 
frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" tabindex="0" vspace="0" width="100%" id="I0_1443515785671" name="I0_1443515785671" src="https://apis.google.com/se/0/_/+1/fastbutton?usegapi=1&size=medium&count=false&origin=http%3A%2F%2Fwww.vineetmanohar.com&url=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&gsrc=3p&ic=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.vi.5hpnngUu-2A.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCPTSqOYkaP1U6q4oCWtRMtgv6oPUA#_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart%2Concircled%2Cdrefresh%2Cerefresh&id=I0_1443515785671&parent=http%3A%2F%2Fwww.vineetmanohar.com&pfname=&rpctoken=42774078" data-gapiattached="true" title="+1" style="position: static; top: 0px; width: 32px; margin: 0px; border-style: none; left: 0px; visibility: visible; height: 20px;">

Related posts:

  1. The plugin ‘org.codehaus.mojo:selenium-maven-plugin’ does not exist or no valid version could be found
  2. Tweet your builds with Maven Twitter Plugin
  3. How to automate project versioning and release with Maven
  4. JAXB code snippets for beginners
  5. How to display maven project version in your webapp
November 2nd, 2009 | Tags:  java,  maven,  maven exec plugin,  maven java,  maven plugin,  mvn,  pom.xml | Category:  java,  Tech |  21 comments

21 comments to 3 ways to run Java main from Maven

  • Erik
    November 4th, 2009 at 6:45 am

    Don’t forget the Maven CLI method, it’s waaay faster than anything else!

  • vineet
    December 9th, 2009 at 2:33 am

    If you get the following error:
    Project ID: org.codehaus.mojo:maven-exec-plugin
    POM Location: ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom
    Reason: Not a v4.0.0 POM. for project org.codehaus.mojo:maven-exec-plugin at ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom

    and the following content in the file: ~/.m2/repository/org/apache/maven/plugins/maven-exec-plugin/maven-metadata-java.net.xml


    < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Moved Permanently

    The document has moved here.

    Apache Server at maven-repository.dev.java.net Port 443


    Try the full command line:
    mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

  • Kamal
    June 16th, 2010 at 3:26 pm

    Thanks folks. I am using the maven-exec plugin to run jarsigner and get surprised by the following:
    jarsigner ${project.build.directory}\jarname bla bla bla

    However, assume the value of ${project.build.directory} is C:\somedir\somesubdir, the exec is ripping off all the slashes in the build directory path and tries to pass”

    C:somedirsomeubdir

    Any ideas?
    Thanks a log

  • flurdy
    July 8th, 2010 at 8:33 am

    @Kamal try forwards slashes instead of backslashes

  • Tim
    August 30th, 2010 at 11:15 am

    So how would I java my -javaagent= arg.. exec.args gives it to the class being run…

  • Tim
    August 30th, 2010 at 11:20 am

    Oh I see now. Run export MAVEN_OPTS=-javaagent:.. first.

  • Jesse Glick
    February 16th, 2011 at 7:23 pm

    Consider using exec:exec rather than exec:java for running your own project, unless the code in question is really a bit of build tool. Discussed here: http://maven.40175.n5.nabble.com/Call-System-setProperty-quot-java-awt-headless-quot-true-td3383750.html#a3388567

    (Hi Vineet!)

  • norman rm
    March 15th, 2011 at 6:57 pm

    thanks

  • Max Mohave
    March 17th, 2011 at 10:59 pm

    Dear Vineet:

    thank, I used your info to run my new application by MVN command line. Do you use an IDE with MAVEN to run and if so which one. And lastly, can you tell me how you would use the equivalent of mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

    to run in that IDE?

    Thanks so much.

  • vineet
    March 18th, 2011 at 4:22 pm

    I use Eclipse. I first run “mvn eclipse:eclipse” to export the project into eclipse format. Then import the project by using File -> Import -> Import existing project.

    However, I use mvn from command line and not from inside the IDE.

    There are eclipse plugins for maven (like m2eclipse) that you can use from inside Eclipse but I don’t use them.

  • Max Mohave
    March 18th, 2011 at 6:55 pm

    Thank you. I appreciate your skill and time.
    Sincerely, Max

  • Finn
    April 27th, 2011 at 6:26 am

    Highest quality blog post ever, exactly what I needed. Thank you.

  • Terence
    November 3rd, 2011 at 11:46 pm

    Thanks. Combined with your post and the maven doco, it took me about 10 minutes to have it working and documented.

  • Akilan
    November 30th, 2011 at 10:37 am

    Thanks Vineet. Wonderful blog and exactly what I searched for.

  • Anil Kesariya
    February 2nd, 2012 at 1:42 am

    hello i m anil

    i m first time working with maven.. so i dont that how should we work with it , i got lession that how we can generate jar file from our java file using maven
    so please tell me that how should i work with it..i have only one day dead line..

  • Tensy
    February 2nd, 2012 at 3:29 pm

    Hi Vineet, This post is really useful.
    However, when I try to run the command, I see the following.
    Command: mvn org.codehaus.mojo:exec-maven-plugin:1.2:java -e -Dexec.mainClass=com.myclass.Wsdl2XsdConverter

    An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. com.qpass.googlecarrierbilling.Wsdl2XsdConverter
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    … 16 more
    Caused by: java.lang.ClassNotFoundException: com.myclass.Wsdl2XsdConverter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:284)
    at java.lang.Thread.run(Thread.java:595)

    I run the mvn compile command also prior to running the above mentioned mvn command.
    Any help is greatly appreciated.

  • vineet
    February 2nd, 2012 at 4:38 pm

    Looks right to me.

    I would try the following:
    1) Try mvn -X to generate more debug info.
    2) Also try the other approach as described in section 2) above: “Running in a phase in pom.xml”, see if that works.

  • Ramaraj
    February 27th, 2012 at 8:06 am

    Thank you for your time and effort to create this blog. I have got more info than what i need.

  • andres
    March 1st, 2012 at 5:16 am

    Thanks a lot. but how to package all depedencies into single jar

  • Dev
    April 9th, 2012 at 10:35 am

    Content is very helpful.
    Please tell me how can i debug while executing my main class. I used Eclipse.

    Thanks

  • Yashaswini
    April 25th, 2012 at 2:30 am

    Hi,
    I need to trigger a makefile through Maven. Could someone please tell how this can be done? Can exec-maven-plugin be used to execute a makefile? When I use exec-maven-plugin to execute my makefile, I get the following error:
    [INFO] — exec-maven-plugin:1.1:exec (buildlib) @ nativeTestProjectMaven —
    [INFO] ‘”C:\Program Files\apache-maven-3.0.4\TestProjectMaven\src\main\native\ma
    kefile”‘ is not recognized as an internal or external command,
    [INFO] operable program or batch file.

Leave a Reply

  

  

  

You can use these HTML tags

name="fb_xdm_frame_http" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_http" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="http://static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;"> name="fb_xdm_frame_https" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_https" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="https://s-static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;">
name="oauth2relay651382484" id="oauth2relay651382484" src="https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.vineetmanohar.com#rpctoken=784954501&forcesecure=1" tabindex="-1" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; width: 1px; height: 1px; position: absolute; top: -100px;">
ShareThis Copy and Paste
- See more at: http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/#sthash.T70JUj6V.dpuf

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?



cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?


id="twttrHubFrameSecure" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrameSecure" src="https://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;"> id="twttrHubFrame" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrame" src="http://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;">
«  Customizing Yahoo! Grids CSS, for beginners  
   How to automate project versioning and release with Maven »

3 ways to run Java main from Maven

Overview

Maven exec plugin lets you run the main method of a Java class in your project, with the project dependencies automatically included in the classpath. This article show you 3 ways of using the maven exec plugin to run java, with code examples.

1) Running from Command line

Since you are not running your code in a maven phase, you first need to compile the code. Remember exec:java does not automatically compile your code, you need to do that first.

  1. mvn compile  

Once your code is compiled, the following command runs your class

Without arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main"  
With arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.args="arg0 arg1 arg2"  
With runtime dependencies in the CLASSPATH:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.classpathScope=runtime  

2) Running in a phase in pom.xml

You can also run the main method in a maven phase. For example, you can run the CodeGenerator.main() method as part of the test phase.

view plain copy to clipboard print ?
  1. <build>  
  2.  <plugins>  
  3.   <plugin>  
  4.    <groupId>org.codehaus.mojo</groupId>  
  5.    <artifactId>exec-maven-plugin</artifactId>  
  6.    <version>1.1.1</version>  
  7.    <executions>  
  8.     <execution>  
  9.      <phase>test</phase>  
  10.      <goals>  
  11.       <goal>java</goal>  
  12.      </goals>  
  13.      <configuration>  
  14.       <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  15.       <arguments>  
  16.        <argument>arg0</argument>  
  17.        <argument>arg1</argument>  
  18.       </arguments>  
  19.      </configuration>  
  20.     </execution>  
  21.    </executions>  
  22.   </plugin>  
  23.  </plugins>  
  24. </build>  

To run the exec plugin with above configuration, simply run the corresponding phase.

  1. mvn test  

3) Running in a profile in pom.xml

You can also run the main method in a different profile. Simply wrap the above config in the <profile> tag.

view plain copy to clipboard print ?
  1. <profiles>  
  2.  <profile>  
  3.   <id>code-generator</id>  
  4.   <build>  
  5.    <plugins>  
  6.     <plugin>  
  7.      <groupId>org.codehaus.mojo</groupId>  
  8.      <artifactId>exec-maven-plugin</artifactId>  
  9.      <version>1.1.1</version>  
  10.      <executions>  
  11.       <execution>  
  12.        <phase>test</phase>  
  13.        <goals>  
  14.         <goal>java</goal>  
  15.        </goals>  
  16.        <configuration>  
  17.         <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  18.         <arguments>  
  19.          <argument>arg0</argument>  
  20.          <argument>arg1</argument>  
  21.         </arguments>  
  22.        </configuration>  
  23.       </execution>  
  24.      </executions>  
  25.     </plugin>  
  26.    </plugins>  
  27.   </build>  
  28.  </profile>  
  29. </profiles>  

To call the above profile, run the following command:

  1. mvn test -Pcode-generator  

Advanced options:

You can get a list of all available parameters by typing:

view plain copy to clipboard print ?
  1. mvn exec:help -Ddetail=true -Dgoal=java  

arguments (exec.arguments)

 The class arguments.

classpathScope (exec.classpathScope, Default: compile)

 Defines the scope of the classpath passed to the plugin. Set to
 compile, test, runtime or system depending on your needs

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
  1. [ERROR] BUILD ERROR  
  2. [INFO] ------------------------------------------------------------------------  
  3. [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:exec-maven-plugin:1.1.1  
  4. on the command line, specify: '-Dexec.arguments=VALUE'  
  5. Cause: Cannot assign configuration entry 'arguments' to 'class [Ljava.lang.String;' from '${exec.arguments}',   
  6. which is of type class java.lang.String  
  7. [INFO] ------------------------------------------------------------------------  
  8. [INFO] Trace  
  9. org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin.   
  10. Reason: Unable to parse the created DOM for plugin configuration  
  11.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:588)  
  12.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)  
  13.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)  
  14.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)  
  15.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)  
  16.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)  
  17.  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)  
  18.  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)  
  19.  at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)  

Solution

exec.arguments was used before version 1.1 of the exec plugin, it did not support conversion of command line String to String[] array.

  1. If possible upgrade to 1.1 or later and use exec.args instead of exec.arguments.
  2. If you can't upgrade the plugin version, you can still use command line arguments with a profile and use multiple <argument> tags associated in the pom.xml

References

    

name="f12f15e27c" width="1000px" height="1000px" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" title="fb:like Facebook Social Plugin" src="http://www.facebook.com/plugins/like.php?app_id=&channel=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter%2F6brUqVNoWO3.js%3Fversion%3D41%23cb%3Df2e7c6ef94%26domain%3Dwww.vineetmanohar.com%26origin%3Dhttp%253A%252F%252Fwww.vineetmanohar.com%252Ff26632479%26relation%3Dparent.parent&container_width=0&href=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&layout=button_count&locale=en_US&sdk=joey&send=false&show_faces=false" style="position: absolute; border-style: none; visibility: visible; width: 78px; height: 20px;">
 
frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" tabindex="0" vspace="0" width="100%" id="I0_1443515785671" name="I0_1443515785671" src="https://apis.google.com/se/0/_/+1/fastbutton?usegapi=1&size=medium&count=false&origin=http%3A%2F%2Fwww.vineetmanohar.com&url=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&gsrc=3p&ic=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.vi.5hpnngUu-2A.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCPTSqOYkaP1U6q4oCWtRMtgv6oPUA#_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart%2Concircled%2Cdrefresh%2Cerefresh&id=I0_1443515785671&parent=http%3A%2F%2Fwww.vineetmanohar.com&pfname=&rpctoken=42774078" data-gapiattached="true" title="+1" style="position: static; top: 0px; width: 32px; margin: 0px; border-style: none; left: 0px; visibility: visible; height: 20px;">

Related posts:

  1. The plugin ‘org.codehaus.mojo:selenium-maven-plugin’ does not exist or no valid version could be found
  2. Tweet your builds with Maven Twitter Plugin
  3. How to automate project versioning and release with Maven
  4. JAXB code snippets for beginners
  5. How to display maven project version in your webapp
November 2nd, 2009 | Tags:  java,  maven,  maven exec plugin,  maven java,  maven plugin,  mvn,  pom.xml | Category:  java,  Tech |  21 comments

21 comments to 3 ways to run Java main from Maven

  • Erik
    November 4th, 2009 at 6:45 am

    Don’t forget the Maven CLI method, it’s waaay faster than anything else!

  • vineet
    December 9th, 2009 at 2:33 am

    If you get the following error:
    Project ID: org.codehaus.mojo:maven-exec-plugin
    POM Location: ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom
    Reason: Not a v4.0.0 POM. for project org.codehaus.mojo:maven-exec-plugin at ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom

    and the following content in the file: ~/.m2/repository/org/apache/maven/plugins/maven-exec-plugin/maven-metadata-java.net.xml


    < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Moved Permanently

    The document has moved here.

    Apache Server at maven-repository.dev.java.net Port 443


    Try the full command line:
    mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

  • Kamal
    June 16th, 2010 at 3:26 pm

    Thanks folks. I am using the maven-exec plugin to run jarsigner and get surprised by the following:
    jarsigner ${project.build.directory}\jarname bla bla bla

    However, assume the value of ${project.build.directory} is C:\somedir\somesubdir, the exec is ripping off all the slashes in the build directory path and tries to pass”

    C:somedirsomeubdir

    Any ideas?
    Thanks a log

  • flurdy
    July 8th, 2010 at 8:33 am

    @Kamal try forwards slashes instead of backslashes

  • Tim
    August 30th, 2010 at 11:15 am

    So how would I java my -javaagent= arg.. exec.args gives it to the class being run…

  • Tim
    August 30th, 2010 at 11:20 am

    Oh I see now. Run export MAVEN_OPTS=-javaagent:.. first.

  • Jesse Glick
    February 16th, 2011 at 7:23 pm

    Consider using exec:exec rather than exec:java for running your own project, unless the code in question is really a bit of build tool. Discussed here: http://maven.40175.n5.nabble.com/Call-System-setProperty-quot-java-awt-headless-quot-true-td3383750.html#a3388567

    (Hi Vineet!)

  • norman rm
    March 15th, 2011 at 6:57 pm

    thanks

  • Max Mohave
    March 17th, 2011 at 10:59 pm

    Dear Vineet:

    thank, I used your info to run my new application by MVN command line. Do you use an IDE with MAVEN to run and if so which one. And lastly, can you tell me how you would use the equivalent of mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

    to run in that IDE?

    Thanks so much.

  • vineet
    March 18th, 2011 at 4:22 pm

    I use Eclipse. I first run “mvn eclipse:eclipse” to export the project into eclipse format. Then import the project by using File -> Import -> Import existing project.

    However, I use mvn from command line and not from inside the IDE.

    There are eclipse plugins for maven (like m2eclipse) that you can use from inside Eclipse but I don’t use them.

  • Max Mohave
    March 18th, 2011 at 6:55 pm

    Thank you. I appreciate your skill and time.
    Sincerely, Max

  • Finn
    April 27th, 2011 at 6:26 am

    Highest quality blog post ever, exactly what I needed. Thank you.

  • Terence
    November 3rd, 2011 at 11:46 pm

    Thanks. Combined with your post and the maven doco, it took me about 10 minutes to have it working and documented.

  • Akilan
    November 30th, 2011 at 10:37 am

    Thanks Vineet. Wonderful blog and exactly what I searched for.

  • Anil Kesariya
    February 2nd, 2012 at 1:42 am

    hello i m anil

    i m first time working with maven.. so i dont that how should we work with it , i got lession that how we can generate jar file from our java file using maven
    so please tell me that how should i work with it..i have only one day dead line..

  • Tensy
    February 2nd, 2012 at 3:29 pm

    Hi Vineet, This post is really useful.
    However, when I try to run the command, I see the following.
    Command: mvn org.codehaus.mojo:exec-maven-plugin:1.2:java -e -Dexec.mainClass=com.myclass.Wsdl2XsdConverter

    An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. com.qpass.googlecarrierbilling.Wsdl2XsdConverter
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    … 16 more
    Caused by: java.lang.ClassNotFoundException: com.myclass.Wsdl2XsdConverter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:284)
    at java.lang.Thread.run(Thread.java:595)

    I run the mvn compile command also prior to running the above mentioned mvn command.
    Any help is greatly appreciated.

  • vineet
    February 2nd, 2012 at 4:38 pm

    Looks right to me.

    I would try the following:
    1) Try mvn -X to generate more debug info.
    2) Also try the other approach as described in section 2) above: “Running in a phase in pom.xml”, see if that works.

  • Ramaraj
    February 27th, 2012 at 8:06 am

    Thank you for your time and effort to create this blog. I have got more info than what i need.

  • andres
    March 1st, 2012 at 5:16 am

    Thanks a lot. but how to package all depedencies into single jar

  • Dev
    April 9th, 2012 at 10:35 am

    Content is very helpful.
    Please tell me how can i debug while executing my main class. I used Eclipse.

    Thanks

  • Yashaswini
    April 25th, 2012 at 2:30 am

    Hi,
    I need to trigger a makefile through Maven. Could someone please tell how this can be done? Can exec-maven-plugin be used to execute a makefile? When I use exec-maven-plugin to execute my makefile, I get the following error:
    [INFO] — exec-maven-plugin:1.1:exec (buildlib) @ nativeTestProjectMaven —
    [INFO] ‘”C:\Program Files\apache-maven-3.0.4\TestProjectMaven\src\main\native\ma
    kefile”‘ is not recognized as an internal or external command,
    [INFO] operable program or batch file.

Leave a Reply

  

  

  

You can use these HTML tags

name="fb_xdm_frame_http" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_http" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="http://static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;"> name="fb_xdm_frame_https" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_https" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="https://s-static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;">
name="oauth2relay651382484" id="oauth2relay651382484" src="https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.vineetmanohar.com#rpctoken=784954501&forcesecure=1" tabindex="-1" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; width: 1px; height: 1px; position: absolute; top: -100px;">
ShareThis Copy and Paste
- See more at: http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/#sthash.T70JUj6V.dpuf id="twttrHubFrameSecure" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrameSecure" src="https://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;"> id="twttrHubFrame" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrame" src="http://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;">
«  Customizing Yahoo! Grids CSS, for beginners  
   How to automate project versioning and release with Maven »

3 ways to run Java main from Maven

Overview

Maven exec plugin lets you run the main method of a Java class in your project, with the project dependencies automatically included in the classpath. This article show you 3 ways of using the maven exec plugin to run java, with code examples.

1) Running from Command line

Since you are not running your code in a maven phase, you first need to compile the code. Remember exec:java does not automatically compile your code, you need to do that first.

  1. mvn compile  

Once your code is compiled, the following command runs your class

Without arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main"  
With arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.args="arg0 arg1 arg2"  
With runtime dependencies in the CLASSPATH:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.classpathScope=runtime  

2) Running in a phase in pom.xml

You can also run the main method in a maven phase. For example, you can run the CodeGenerator.main() method as part of the test phase.

view plain copy to clipboard print ?
  1. <build>  
  2.  <plugins>  
  3.   <plugin>  
  4.    <groupId>org.codehaus.mojo</groupId>  
  5.    <artifactId>exec-maven-plugin</artifactId>  
  6.    <version>1.1.1</version>  
  7.    <executions>  
  8.     <execution>  
  9.      <phase>test</phase>  
  10.      <goals>  
  11.       <goal>java</goal>  
  12.      </goals>  
  13.      <configuration>  
  14.       <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  15.       <arguments>  
  16.        <argument>arg0</argument>  
  17.        <argument>arg1</argument>  
  18.       </arguments>  
  19.      </configuration>  
  20.     </execution>  
  21.    </executions>  
  22.   </plugin>  
  23.  </plugins>  
  24. </build>  

To run the exec plugin with above configuration, simply run the corresponding phase.

  1. mvn test  

3) Running in a profile in pom.xml

You can also run the main method in a different profile. Simply wrap the above config in the <profile> tag.

view plain copy to clipboard print ?
  1. <profiles>  
  2.  <profile>  
  3.   <id>code-generator</id>  
  4.   <build>  
  5.    <plugins>  
  6.     <plugin>  
  7.      <groupId>org.codehaus.mojo</groupId>  
  8.      <artifactId>exec-maven-plugin</artifactId>  
  9.      <version>1.1.1</version>  
  10.      <executions>  
  11.       <execution>  
  12.        <phase>test</phase>  
  13.        <goals>  
  14.         <goal>java</goal>  
  15.        </goals>  
  16.        <configuration>  
  17.         <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  18.         <arguments>  
  19.          <argument>arg0</argument>  
  20.          <argument>arg1</argument>  
  21.         </arguments>  
  22.        </configuration>  
  23.       </execution>  
  24.      </executions>  
  25.     </plugin>  
  26.    </plugins>  
  27.   </build>  
  28.  </profile>  
  29. </profiles>  

To call the above profile, run the following command:

  1. mvn test -Pcode-generator  

Advanced options:

You can get a list of all available parameters by typing:

view plain copy to clipboard print ?
  1. mvn exec:help -Ddetail=true -Dgoal=java  

arguments (exec.arguments)

 The class arguments.

classpathScope (exec.classpathScope, Default: compile)

 Defines the scope of the classpath passed to the plugin. Set to
 compile, test, runtime or system depending on your needs

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
  1. [ERROR] BUILD ERROR  
  2. [INFO] ------------------------------------------------------------------------  
  3. [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:exec-maven-plugin:1.1.1  
  4. on the command line, specify: '-Dexec.arguments=VALUE'  
  5. Cause: Cannot assign configuration entry 'arguments' to 'class [Ljava.lang.String;' from '${exec.arguments}',   
  6. which is of type class java.lang.String  
  7. [INFO] ------------------------------------------------------------------------  
  8. [INFO] Trace  
  9. org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin.   
  10. Reason: Unable to parse the created DOM for plugin configuration  
  11.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:588)  
  12.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)  
  13.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)  
  14.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)  
  15.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)  
  16.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)  
  17.  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)  
  18.  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)  
  19.  at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)  

Solution

exec.arguments was used before version 1.1 of the exec plugin, it did not support conversion of command line String to String[] array.

  1. If possible upgrade to 1.1 or later and use exec.args instead of exec.arguments.
  2. If you can't upgrade the plugin version, you can still use command line arguments with a profile and use multiple <argument> tags associated in the pom.xml

References

    

name="f12f15e27c" width="1000px" height="1000px" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" title="fb:like Facebook Social Plugin" src="http://www.facebook.com/plugins/like.php?app_id=&channel=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter%2F6brUqVNoWO3.js%3Fversion%3D41%23cb%3Df2e7c6ef94%26domain%3Dwww.vineetmanohar.com%26origin%3Dhttp%253A%252F%252Fwww.vineetmanohar.com%252Ff26632479%26relation%3Dparent.parent&container_width=0&href=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&layout=button_count&locale=en_US&sdk=joey&send=false&show_faces=false" style="position: absolute; border-style: none; visibility: visible; width: 78px; height: 20px;">
 
frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" tabindex="0" vspace="0" width="100%" id="I0_1443515785671" name="I0_1443515785671" src="https://apis.google.com/se/0/_/+1/fastbutton?usegapi=1&size=medium&count=false&origin=http%3A%2F%2Fwww.vineetmanohar.com&url=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&gsrc=3p&ic=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.vi.5hpnngUu-2A.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCPTSqOYkaP1U6q4oCWtRMtgv6oPUA#_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart%2Concircled%2Cdrefresh%2Cerefresh&id=I0_1443515785671&parent=http%3A%2F%2Fwww.vineetmanohar.com&pfname=&rpctoken=42774078" data-gapiattached="true" title="+1" style="position: static; top: 0px; width: 32px; margin: 0px; border-style: none; left: 0px; visibility: visible; height: 20px;">

Related posts:

  1. The plugin ‘org.codehaus.mojo:selenium-maven-plugin’ does not exist or no valid version could be found
  2. Tweet your builds with Maven Twitter Plugin
  3. How to automate project versioning and release with Maven
  4. JAXB code snippets for beginners
  5. How to display maven project version in your webapp
November 2nd, 2009 | Tags:  java,  maven,  maven exec plugin,  maven java,  maven plugin,  mvn,  pom.xml | Category:  java,  Tech |  21 comments

21 comments to 3 ways to run Java main from Maven

  • Erik
    November 4th, 2009 at 6:45 am

    Don’t forget the Maven CLI method, it’s waaay faster than anything else!

  • vineet
    December 9th, 2009 at 2:33 am

    If you get the following error:
    Project ID: org.codehaus.mojo:maven-exec-plugin
    POM Location: ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom
    Reason: Not a v4.0.0 POM. for project org.codehaus.mojo:maven-exec-plugin at ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom

    and the following content in the file: ~/.m2/repository/org/apache/maven/plugins/maven-exec-plugin/maven-metadata-java.net.xml


    < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Moved Permanently

    The document has moved here.

    Apache Server at maven-repository.dev.java.net Port 443


    Try the full command line:
    mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

  • Kamal
    June 16th, 2010 at 3:26 pm

    Thanks folks. I am using the maven-exec plugin to run jarsigner and get surprised by the following:
    jarsigner ${project.build.directory}\jarname bla bla bla

    However, assume the value of ${project.build.directory} is C:\somedir\somesubdir, the exec is ripping off all the slashes in the build directory path and tries to pass”

    C:somedirsomeubdir

    Any ideas?
    Thanks a log

  • flurdy
    July 8th, 2010 at 8:33 am

    @Kamal try forwards slashes instead of backslashes

  • Tim
    August 30th, 2010 at 11:15 am

    So how would I java my -javaagent= arg.. exec.args gives it to the class being run…

  • Tim
    August 30th, 2010 at 11:20 am

    Oh I see now. Run export MAVEN_OPTS=-javaagent:.. first.

  • Jesse Glick
    February 16th, 2011 at 7:23 pm

    Consider using exec:exec rather than exec:java for running your own project, unless the code in question is really a bit of build tool. Discussed here: http://maven.40175.n5.nabble.com/Call-System-setProperty-quot-java-awt-headless-quot-true-td3383750.html#a3388567

    (Hi Vineet!)

  • norman rm
    March 15th, 2011 at 6:57 pm

    thanks

  • Max Mohave
    March 17th, 2011 at 10:59 pm

    Dear Vineet:

    thank, I used your info to run my new application by MVN command line. Do you use an IDE with MAVEN to run and if so which one. And lastly, can you tell me how you would use the equivalent of mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

    to run in that IDE?

    Thanks so much.

  • vineet
    March 18th, 2011 at 4:22 pm

    I use Eclipse. I first run “mvn eclipse:eclipse” to export the project into eclipse format. Then import the project by using File -> Import -> Import existing project.

    However, I use mvn from command line and not from inside the IDE.

    There are eclipse plugins for maven (like m2eclipse) that you can use from inside Eclipse but I don’t use them.

  • Max Mohave
    March 18th, 2011 at 6:55 pm

    Thank you. I appreciate your skill and time.
    Sincerely, Max

  • Finn
    April 27th, 2011 at 6:26 am

    Highest quality blog post ever, exactly what I needed. Thank you.

  • Terence
    November 3rd, 2011 at 11:46 pm

    Thanks. Combined with your post and the maven doco, it took me about 10 minutes to have it working and documented.

  • Akilan
    November 30th, 2011 at 10:37 am

    Thanks Vineet. Wonderful blog and exactly what I searched for.

  • Anil Kesariya
    February 2nd, 2012 at 1:42 am

    hello i m anil

    i m first time working with maven.. so i dont that how should we work with it , i got lession that how we can generate jar file from our java file using maven
    so please tell me that how should i work with it..i have only one day dead line..

  • Tensy
    February 2nd, 2012 at 3:29 pm

    Hi Vineet, This post is really useful.
    However, when I try to run the command, I see the following.
    Command: mvn org.codehaus.mojo:exec-maven-plugin:1.2:java -e -Dexec.mainClass=com.myclass.Wsdl2XsdConverter

    An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. com.qpass.googlecarrierbilling.Wsdl2XsdConverter
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    … 16 more
    Caused by: java.lang.ClassNotFoundException: com.myclass.Wsdl2XsdConverter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:284)
    at java.lang.Thread.run(Thread.java:595)

    I run the mvn compile command also prior to running the above mentioned mvn command.
    Any help is greatly appreciated.

  • vineet
    February 2nd, 2012 at 4:38 pm

    Looks right to me.

    I would try the following:
    1) Try mvn -X to generate more debug info.
    2) Also try the other approach as described in section 2) above: “Running in a phase in pom.xml”, see if that works.

  • Ramaraj
    February 27th, 2012 at 8:06 am

    Thank you for your time and effort to create this blog. I have got more info than what i need.

  • andres
    March 1st, 2012 at 5:16 am

    Thanks a lot. but how to package all depedencies into single jar

  • Dev
    April 9th, 2012 at 10:35 am

    Content is very helpful.
    Please tell me how can i debug while executing my main class. I used Eclipse.

    Thanks

  • Yashaswini
    April 25th, 2012 at 2:30 am

    Hi,
    I need to trigger a makefile through Maven. Could someone please tell how this can be done? Can exec-maven-plugin be used to execute a makefile? When I use exec-maven-plugin to execute my makefile, I get the following error:
    [INFO] — exec-maven-plugin:1.1:exec (buildlib) @ nativeTestProjectMaven —
    [INFO] ‘”C:\Program Files\apache-maven-3.0.4\TestProjectMaven\src\main\native\ma
    kefile”‘ is not recognized as an internal or external command,
    [INFO] operable program or batch file.

Leave a Reply

  

  

  

You can use these HTML tags

name="fb_xdm_frame_http" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_http" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="http://static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;"> name="fb_xdm_frame_https" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_https" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="https://s-static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;">
name="oauth2relay651382484" id="oauth2relay651382484" src="https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.vineetmanohar.com#rpctoken=784954501&forcesecure=1" tabindex="-1" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; width: 1px; height: 1px; position: absolute; top: -100px;">
ShareThis Copy and Paste
- See more at: http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/#sthash.T70JUj6V.dpuf


cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?


id="twttrHubFrameSecure" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrameSecure" src="https://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;"> id="twttrHubFrame" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrame" src="http://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;">
«  Customizing Yahoo! Grids CSS, for beginners  
   How to automate project versioning and release with Maven »

3 ways to run Java main from Maven

Overview

Maven exec plugin lets you run the main method of a Java class in your project, with the project dependencies automatically included in the classpath. This article show you 3 ways of using the maven exec plugin to run java, with code examples.

1) Running from Command line

Since you are not running your code in a maven phase, you first need to compile the code. Remember exec:java does not automatically compile your code, you need to do that first.

  1. mvn compile  

Once your code is compiled, the following command runs your class

Without arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main"  
With arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.args="arg0 arg1 arg2"  
With runtime dependencies in the CLASSPATH:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.classpathScope=runtime  

2) Running in a phase in pom.xml

You can also run the main method in a maven phase. For example, you can run the CodeGenerator.main() method as part of the test phase.

view plain copy to clipboard print ?
  1. <build>  
  2.  <plugins>  
  3.   <plugin>  
  4.    <groupId>org.codehaus.mojo</groupId>  
  5.    <artifactId>exec-maven-plugin</artifactId>  
  6.    <version>1.1.1</version>  
  7.    <executions>  
  8.     <execution>  
  9.      <phase>test</phase>  
  10.      <goals>  
  11.       <goal>java</goal>  
  12.      </goals>  
  13.      <configuration>  
  14.       <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  15.       <arguments>  
  16.        <argument>arg0</argument>  
  17.        <argument>arg1</argument>  
  18.       </arguments>  
  19.      </configuration>  
  20.     </execution>  
  21.    </executions>  
  22.   </plugin>  
  23.  </plugins>  
  24. </build>  

To run the exec plugin with above configuration, simply run the corresponding phase.

  1. mvn test  

3) Running in a profile in pom.xml

You can also run the main method in a different profile. Simply wrap the above config in the <profile> tag.

view plain copy to clipboard print ?
  1. <profiles>  
  2.  <profile>  
  3.   <id>code-generator</id>  
  4.   <build>  
  5.    <plugins>  
  6.     <plugin>  
  7.      <groupId>org.codehaus.mojo</groupId>  
  8.      <artifactId>exec-maven-plugin</artifactId>  
  9.      <version>1.1.1</version>  
  10.      <executions>  
  11.       <execution>  
  12.        <phase>test</phase>  
  13.        <goals>  
  14.         <goal>java</goal>  
  15.        </goals>  
  16.        <configuration>  
  17.         <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  18.         <arguments>  
  19.          <argument>arg0</argument>  
  20.          <argument>arg1</argument>  
  21.         </arguments>  
  22.        </configuration>  
  23.       </execution>  
  24.      </executions>  
  25.     </plugin>  
  26.    </plugins>  
  27.   </build>  
  28.  </profile>  
  29. </profiles>  

To call the above profile, run the following command:

  1. mvn test -Pcode-generator  

Advanced options:

You can get a list of all available parameters by typing:

view plain copy to clipboard print ?
  1. mvn exec:help -Ddetail=true -Dgoal=java  

arguments (exec.arguments)

 The class arguments.

classpathScope (exec.classpathScope, Default: compile)

 Defines the scope of the classpath passed to the plugin. Set to
 compile, test, runtime or system depending on your needs

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
  1. [ERROR] BUILD ERROR  
  2. [INFO] ------------------------------------------------------------------------  
  3. [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:exec-maven-plugin:1.1.1  
  4. on the command line, specify: '-Dexec.arguments=VALUE'  
  5. Cause: Cannot assign configuration entry 'arguments' to 'class [Ljava.lang.String;' from '${exec.arguments}',   
  6. which is of type class java.lang.String  
  7. [INFO] ------------------------------------------------------------------------  
  8. [INFO] Trace  
  9. org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin.   
  10. Reason: Unable to parse the created DOM for plugin configuration  
  11.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:588)  
  12.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)  
  13.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)  
  14.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)  
  15.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)  
  16.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)  
  17.  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)  
  18.  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)  
  19.  at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)  

Solution

exec.arguments was used before version 1.1 of the exec plugin, it did not support conversion of command line String to String[] array.

  1. If possible upgrade to 1.1 or later and use exec.args instead of exec.arguments.
  2. If you can't upgrade the plugin version, you can still use command line arguments with a profile and use multiple <argument> tags associated in the pom.xml

References

    

name="f12f15e27c" width="1000px" height="1000px" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" title="fb:like Facebook Social Plugin" src="http://www.facebook.com/plugins/like.php?app_id=&channel=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter%2F6brUqVNoWO3.js%3Fversion%3D41%23cb%3Df2e7c6ef94%26domain%3Dwww.vineetmanohar.com%26origin%3Dhttp%253A%252F%252Fwww.vineetmanohar.com%252Ff26632479%26relation%3Dparent.parent&container_width=0&href=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&layout=button_count&locale=en_US&sdk=joey&send=false&show_faces=false" style="position: absolute; border-style: none; visibility: visible; width: 78px; height: 20px;">
 
frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" tabindex="0" vspace="0" width="100%" id="I0_1443515785671" name="I0_1443515785671" src="https://apis.google.com/se/0/_/+1/fastbutton?usegapi=1&size=medium&count=false&origin=http%3A%2F%2Fwww.vineetmanohar.com&url=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&gsrc=3p&ic=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.vi.5hpnngUu-2A.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCPTSqOYkaP1U6q4oCWtRMtgv6oPUA#_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart%2Concircled%2Cdrefresh%2Cerefresh&id=I0_1443515785671&parent=http%3A%2F%2Fwww.vineetmanohar.com&pfname=&rpctoken=42774078" data-gapiattached="true" title="+1" style="position: static; top: 0px; width: 32px; margin: 0px; border-style: none; left: 0px; visibility: visible; height: 20px;">

Related posts:

  1. The plugin ‘org.codehaus.mojo:selenium-maven-plugin’ does not exist or no valid version could be found
  2. Tweet your builds with Maven Twitter Plugin
  3. How to automate project versioning and release with Maven
  4. JAXB code snippets for beginners
  5. How to display maven project version in your webapp
November 2nd, 2009 | Tags:  java,  maven,  maven exec plugin,  maven java,  maven plugin,  mvn,  pom.xml | Category:  java,  Tech |  21 comments

21 comments to 3 ways to run Java main from Maven

  • Erik
    November 4th, 2009 at 6:45 am

    Don’t forget the Maven CLI method, it’s waaay faster than anything else!

  • vineet
    December 9th, 2009 at 2:33 am

    If you get the following error:
    Project ID: org.codehaus.mojo:maven-exec-plugin
    POM Location: ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom
    Reason: Not a v4.0.0 POM. for project org.codehaus.mojo:maven-exec-plugin at ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom

    and the following content in the file: ~/.m2/repository/org/apache/maven/plugins/maven-exec-plugin/maven-metadata-java.net.xml


    < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Moved Permanently

    The document has moved here.

    Apache Server at maven-repository.dev.java.net Port 443


    Try the full command line:
    mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

  • Kamal
    June 16th, 2010 at 3:26 pm

    Thanks folks. I am using the maven-exec plugin to run jarsigner and get surprised by the following:
    jarsigner ${project.build.directory}\jarname bla bla bla

    However, assume the value of ${project.build.directory} is C:\somedir\somesubdir, the exec is ripping off all the slashes in the build directory path and tries to pass”

    C:somedirsomeubdir

    Any ideas?
    Thanks a log

  • flurdy
    July 8th, 2010 at 8:33 am

    @Kamal try forwards slashes instead of backslashes

  • Tim
    August 30th, 2010 at 11:15 am

    So how would I java my -javaagent= arg.. exec.args gives it to the class being run…

  • Tim
    August 30th, 2010 at 11:20 am

    Oh I see now. Run export MAVEN_OPTS=-javaagent:.. first.

  • Jesse Glick
    February 16th, 2011 at 7:23 pm

    Consider using exec:exec rather than exec:java for running your own project, unless the code in question is really a bit of build tool. Discussed here: http://maven.40175.n5.nabble.com/Call-System-setProperty-quot-java-awt-headless-quot-true-td3383750.html#a3388567

    (Hi Vineet!)

  • norman rm
    March 15th, 2011 at 6:57 pm

    thanks

  • Max Mohave
    March 17th, 2011 at 10:59 pm

    Dear Vineet:

    thank, I used your info to run my new application by MVN command line. Do you use an IDE with MAVEN to run and if so which one. And lastly, can you tell me how you would use the equivalent of mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

    to run in that IDE?

    Thanks so much.

  • vineet
    March 18th, 2011 at 4:22 pm

    I use Eclipse. I first run “mvn eclipse:eclipse” to export the project into eclipse format. Then import the project by using File -> Import -> Import existing project.

    However, I use mvn from command line and not from inside the IDE.

    There are eclipse plugins for maven (like m2eclipse) that you can use from inside Eclipse but I don’t use them.

  • Max Mohave
    March 18th, 2011 at 6:55 pm

    Thank you. I appreciate your skill and time.
    Sincerely, Max

  • Finn
    April 27th, 2011 at 6:26 am

    Highest quality blog post ever, exactly what I needed. Thank you.

  • Terence
    November 3rd, 2011 at 11:46 pm

    Thanks. Combined with your post and the maven doco, it took me about 10 minutes to have it working and documented.

  • Akilan
    November 30th, 2011 at 10:37 am

    Thanks Vineet. Wonderful blog and exactly what I searched for.

  • Anil Kesariya
    February 2nd, 2012 at 1:42 am

    hello i m anil

    i m first time working with maven.. so i dont that how should we work with it , i got lession that how we can generate jar file from our java file using maven
    so please tell me that how should i work with it..i have only one day dead line..

  • Tensy
    February 2nd, 2012 at 3:29 pm

    Hi Vineet, This post is really useful.
    However, when I try to run the command, I see the following.
    Command: mvn org.codehaus.mojo:exec-maven-plugin:1.2:java -e -Dexec.mainClass=com.myclass.Wsdl2XsdConverter

    An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. com.qpass.googlecarrierbilling.Wsdl2XsdConverter
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    … 16 more
    Caused by: java.lang.ClassNotFoundException: com.myclass.Wsdl2XsdConverter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:284)
    at java.lang.Thread.run(Thread.java:595)

    I run the mvn compile command also prior to running the above mentioned mvn command.
    Any help is greatly appreciated.

  • vineet
    February 2nd, 2012 at 4:38 pm

    Looks right to me.

    I would try the following:
    1) Try mvn -X to generate more debug info.
    2) Also try the other approach as described in section 2) above: “Running in a phase in pom.xml”, see if that works.

  • Ramaraj
    February 27th, 2012 at 8:06 am

    Thank you for your time and effort to create this blog. I have got more info than what i need.

  • andres
    March 1st, 2012 at 5:16 am

    Thanks a lot. but how to package all depedencies into single jar

  • Dev
    April 9th, 2012 at 10:35 am

    Content is very helpful.
    Please tell me how can i debug while executing my main class. I used Eclipse.

    Thanks

  • Yashaswini
    April 25th, 2012 at 2:30 am

    Hi,
    I need to trigger a makefile through Maven. Could someone please tell how this can be done? Can exec-maven-plugin be used to execute a makefile? When I use exec-maven-plugin to execute my makefile, I get the following error:
    [INFO] — exec-maven-plugin:1.1:exec (buildlib) @ nativeTestProjectMaven —
    [INFO] ‘”C:\Program Files\apache-maven-3.0.4\TestProjectMaven\src\main\native\ma
    kefile”‘ is not recognized as an internal or external command,
    [INFO] operable program or batch file.

Leave a Reply

  

  

  

You can use these HTML tags

name="fb_xdm_frame_http" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_http" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="http://static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;"> name="fb_xdm_frame_https" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_https" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="https://s-static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;">
name="oauth2relay651382484" id="oauth2relay651382484" src="https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.vineetmanohar.com#rpctoken=784954501&forcesecure=1" tabindex="-1" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; width: 1px; height: 1px; position: absolute; top: -100px;">
ShareThis Copy and Paste
- See more at: http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/#sthash.T70JUj6V.dpuf id="twttrHubFrameSecure" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrameSecure" src="https://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;"> id="twttrHubFrame" allowtransparency="true" frameborder="0" scrolling="no" tabindex="0" name="twttrHubFrame" src="http://platform.twitter.com/widgets/hub.bd32c94b5665aa746e00aaa2cf9de3cf.html" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; position: absolute; top: -9999em; width: 10px; height: 10px;">
«  Customizing Yahoo! Grids CSS, for beginners  
   How to automate project versioning and release with Maven »

3 ways to run Java main from Maven

Overview

Maven exec plugin lets you run the main method of a Java class in your project, with the project dependencies automatically included in the classpath. This article show you 3 ways of using the maven exec plugin to run java, with code examples.

1) Running from Command line

Since you are not running your code in a maven phase, you first need to compile the code. Remember exec:java does not automatically compile your code, you need to do that first.

  1. mvn compile  

Once your code is compiled, the following command runs your class

Without arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main"  
With arguments:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.args="arg0 arg1 arg2"  
With runtime dependencies in the CLASSPATH:
view plain copy to clipboard print ?
  1. mvn exec:java -Dexec.mainClass="com.vineetmanohar.module.Main" -Dexec.classpathScope=runtime  

2) Running in a phase in pom.xml

You can also run the main method in a maven phase. For example, you can run the CodeGenerator.main() method as part of the test phase.

view plain copy to clipboard print ?
  1. <build>  
  2.  <plugins>  
  3.   <plugin>  
  4.    <groupId>org.codehaus.mojo</groupId>  
  5.    <artifactId>exec-maven-plugin</artifactId>  
  6.    <version>1.1.1</version>  
  7.    <executions>  
  8.     <execution>  
  9.      <phase>test</phase>  
  10.      <goals>  
  11.       <goal>java</goal>  
  12.      </goals>  
  13.      <configuration>  
  14.       <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  15.       <arguments>  
  16.        <argument>arg0</argument>  
  17.        <argument>arg1</argument>  
  18.       </arguments>  
  19.      </configuration>  
  20.     </execution>  
  21.    </executions>  
  22.   </plugin>  
  23.  </plugins>  
  24. </build>  

To run the exec plugin with above configuration, simply run the corresponding phase.

  1. mvn test  

3) Running in a profile in pom.xml

You can also run the main method in a different profile. Simply wrap the above config in the <profile> tag.

view plain copy to clipboard print ?
  1. <profiles>  
  2.  <profile>  
  3.   <id>code-generator</id>  
  4.   <build>  
  5.    <plugins>  
  6.     <plugin>  
  7.      <groupId>org.codehaus.mojo</groupId>  
  8.      <artifactId>exec-maven-plugin</artifactId>  
  9.      <version>1.1.1</version>  
  10.      <executions>  
  11.       <execution>  
  12.        <phase>test</phase>  
  13.        <goals>  
  14.         <goal>java</goal>  
  15.        </goals>  
  16.        <configuration>  
  17.         <mainClass>com.vineetmanohar.module.CodeGenerator</mainClass>  
  18.         <arguments>  
  19.          <argument>arg0</argument>  
  20.          <argument>arg1</argument>  
  21.         </arguments>  
  22.        </configuration>  
  23.       </execution>  
  24.      </executions>  
  25.     </plugin>  
  26.    </plugins>  
  27.   </build>  
  28.  </profile>  
  29. </profiles>  

To call the above profile, run the following command:

  1. mvn test -Pcode-generator  

Advanced options:

You can get a list of all available parameters by typing:

view plain copy to clipboard print ?
  1. mvn exec:help -Ddetail=true -Dgoal=java  

arguments (exec.arguments)

 The class arguments.

classpathScope (exec.classpathScope, Default: compile)

 Defines the scope of the classpath passed to the plugin. Set to
 compile, test, runtime or system depending on your needs

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
  1. [ERROR] BUILD ERROR  
  2. [INFO] ------------------------------------------------------------------------  
  3. [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:exec-maven-plugin:1.1.1  
  4. on the command line, specify: '-Dexec.arguments=VALUE'  
  5. Cause: Cannot assign configuration entry 'arguments' to 'class [Ljava.lang.String;' from '${exec.arguments}',   
  6. which is of type class java.lang.String  
  7. [INFO] ------------------------------------------------------------------------  
  8. [INFO] Trace  
  9. org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin.   
  10. Reason: Unable to parse the created DOM for plugin configuration  
  11.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:588)  
  12.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)  
  13.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)  
  14.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)  
  15.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)  
  16.  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)  
  17.  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)  
  18.  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)  
  19.  at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)  

Solution

exec.arguments was used before version 1.1 of the exec plugin, it did not support conversion of command line String to String[] array.

  1. If possible upgrade to 1.1 or later and use exec.args instead of exec.arguments.
  2. If you can't upgrade the plugin version, you can still use command line arguments with a profile and use multiple <argument> tags associated in the pom.xml

References

    

name="f12f15e27c" width="1000px" height="1000px" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" title="fb:like Facebook Social Plugin" src="http://www.facebook.com/plugins/like.php?app_id=&channel=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter%2F6brUqVNoWO3.js%3Fversion%3D41%23cb%3Df2e7c6ef94%26domain%3Dwww.vineetmanohar.com%26origin%3Dhttp%253A%252F%252Fwww.vineetmanohar.com%252Ff26632479%26relation%3Dparent.parent&container_width=0&href=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&layout=button_count&locale=en_US&sdk=joey&send=false&show_faces=false" style="position: absolute; border-style: none; visibility: visible; width: 78px; height: 20px;">
 
frameborder="0" hspace="0" marginheight="0" marginwidth="0" scrolling="no" tabindex="0" vspace="0" width="100%" id="I0_1443515785671" name="I0_1443515785671" src="https://apis.google.com/se/0/_/+1/fastbutton?usegapi=1&size=medium&count=false&origin=http%3A%2F%2Fwww.vineetmanohar.com&url=http%3A%2F%2Fwww.vineetmanohar.com%2F2009%2F11%2F3-ways-to-run-java-main-from-maven%2F&gsrc=3p&ic=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.vi.5hpnngUu-2A.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCPTSqOYkaP1U6q4oCWtRMtgv6oPUA#_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart%2Concircled%2Cdrefresh%2Cerefresh&id=I0_1443515785671&parent=http%3A%2F%2Fwww.vineetmanohar.com&pfname=&rpctoken=42774078" data-gapiattached="true" title="+1" style="position: static; top: 0px; width: 32px; margin: 0px; border-style: none; left: 0px; visibility: visible; height: 20px;">

Related posts:

  1. The plugin ‘org.codehaus.mojo:selenium-maven-plugin’ does not exist or no valid version could be found
  2. Tweet your builds with Maven Twitter Plugin
  3. How to automate project versioning and release with Maven
  4. JAXB code snippets for beginners
  5. How to display maven project version in your webapp
November 2nd, 2009 | Tags:  java,  maven,  maven exec plugin,  maven java,  maven plugin,  mvn,  pom.xml | Category:  java,  Tech |  21 comments

21 comments to 3 ways to run Java main from Maven

  • Erik
    November 4th, 2009 at 6:45 am

    Don’t forget the Maven CLI method, it’s waaay faster than anything else!

  • vineet
    December 9th, 2009 at 2:33 am

    If you get the following error:
    Project ID: org.codehaus.mojo:maven-exec-plugin
    POM Location: ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom
    Reason: Not a v4.0.0 POM. for project org.codehaus.mojo:maven-exec-plugin at ~/.m2/repository/org/codehaus/mojo/maven-exec-plugin/1.1.1/maven-exec-plugin-1.1.1.pom

    and the following content in the file: ~/.m2/repository/org/apache/maven/plugins/maven-exec-plugin/maven-metadata-java.net.xml


    < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Moved Permanently

    The document has moved here.

    Apache Server at maven-repository.dev.java.net Port 443


    Try the full command line:
    mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

  • Kamal
    June 16th, 2010 at 3:26 pm

    Thanks folks. I am using the maven-exec plugin to run jarsigner and get surprised by the following:
    jarsigner ${project.build.directory}\jarname bla bla bla

    However, assume the value of ${project.build.directory} is C:\somedir\somesubdir, the exec is ripping off all the slashes in the build directory path and tries to pass”

    C:somedirsomeubdir

    Any ideas?
    Thanks a log

  • flurdy
    July 8th, 2010 at 8:33 am

    @Kamal try forwards slashes instead of backslashes

  • Tim
    August 30th, 2010 at 11:15 am

    So how would I java my -javaagent= arg.. exec.args gives it to the class being run…

  • Tim
    August 30th, 2010 at 11:20 am

    Oh I see now. Run export MAVEN_OPTS=-javaagent:.. first.

  • Jesse Glick
    February 16th, 2011 at 7:23 pm

    Consider using exec:exec rather than exec:java for running your own project, unless the code in question is really a bit of build tool. Discussed here: http://maven.40175.n5.nabble.com/Call-System-setProperty-quot-java-awt-headless-quot-true-td3383750.html#a3388567

    (Hi Vineet!)

  • norman rm
    March 15th, 2011 at 6:57 pm

    thanks

  • Max Mohave
    March 17th, 2011 at 10:59 pm

    Dear Vineet:

    thank, I used your info to run my new application by MVN command line. Do you use an IDE with MAVEN to run and if so which one. And lastly, can you tell me how you would use the equivalent of mvn org.codehaus.mojo:exec-maven-plugin:1.1.1:java -Dexec.mainClass=com.vineetmanohar.module.Main

    to run in that IDE?

    Thanks so much.

  • vineet
    March 18th, 2011 at 4:22 pm

    I use Eclipse. I first run “mvn eclipse:eclipse” to export the project into eclipse format. Then import the project by using File -> Import -> Import existing project.

    However, I use mvn from command line and not from inside the IDE.

    There are eclipse plugins for maven (like m2eclipse) that you can use from inside Eclipse but I don’t use them.

  • Max Mohave
    March 18th, 2011 at 6:55 pm

    Thank you. I appreciate your skill and time.
    Sincerely, Max

  • Finn
    April 27th, 2011 at 6:26 am

    Highest quality blog post ever, exactly what I needed. Thank you.

  • Terence
    November 3rd, 2011 at 11:46 pm

    Thanks. Combined with your post and the maven doco, it took me about 10 minutes to have it working and documented.

  • Akilan
    November 30th, 2011 at 10:37 am

    Thanks Vineet. Wonderful blog and exactly what I searched for.

  • Anil Kesariya
    February 2nd, 2012 at 1:42 am

    hello i m anil

    i m first time working with maven.. so i dont that how should we work with it , i got lession that how we can generate jar file from our java file using maven
    so please tell me that how should i work with it..i have only one day dead line..

  • Tensy
    February 2nd, 2012 at 3:29 pm

    Hi Vineet, This post is really useful.
    However, when I try to run the command, I see the following.
    Command: mvn org.codehaus.mojo:exec-maven-plugin:1.2:java -e -Dexec.mainClass=com.myclass.Wsdl2XsdConverter

    An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    INFO] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. com.myclass.Wsdl2XsdConverter
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. com.qpass.googlecarrierbilling.Wsdl2XsdConverter
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
    … 16 more
    Caused by: java.lang.ClassNotFoundException: com.myclass.Wsdl2XsdConverter
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:284)
    at java.lang.Thread.run(Thread.java:595)

    I run the mvn compile command also prior to running the above mentioned mvn command.
    Any help is greatly appreciated.

  • vineet
    February 2nd, 2012 at 4:38 pm

    Looks right to me.

    I would try the following:
    1) Try mvn -X to generate more debug info.
    2) Also try the other approach as described in section 2) above: “Running in a phase in pom.xml”, see if that works.

  • Ramaraj
    February 27th, 2012 at 8:06 am

    Thank you for your time and effort to create this blog. I have got more info than what i need.

  • andres
    March 1st, 2012 at 5:16 am

    Thanks a lot. but how to package all depedencies into single jar

  • Dev
    April 9th, 2012 at 10:35 am

    Content is very helpful.
    Please tell me how can i debug while executing my main class. I used Eclipse.

    Thanks

  • Yashaswini
    April 25th, 2012 at 2:30 am

    Hi,
    I need to trigger a makefile through Maven. Could someone please tell how this can be done? Can exec-maven-plugin be used to execute a makefile? When I use exec-maven-plugin to execute my makefile, I get the following error:
    [INFO] — exec-maven-plugin:1.1:exec (buildlib) @ nativeTestProjectMaven —
    [INFO] ‘”C:\Program Files\apache-maven-3.0.4\TestProjectMaven\src\main\native\ma
    kefile”‘ is not recognized as an internal or external command,
    [INFO] operable program or batch file.

Leave a Reply

  

  

  

You can use these HTML tags

name="fb_xdm_frame_http" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_http" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="http://static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;"> name="fb_xdm_frame_https" frameborder="0" allowtransparency="true" allowfullscreen="true" scrolling="no" id="fb_xdm_frame_https" aria-hidden="true" title="Facebook Cross Domain Communication Frame" tabindex="-1" src="https://s-static.ak.facebook.com/connect/xd_arbiter/6brUqVNoWO3.js?version=41#channel=f26632479&origin=http%3A%2F%2Fwww.vineetmanohar.com" style="border-style: none;">
name="oauth2relay651382484" id="oauth2relay651382484" src="https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.vineetmanohar.com#rpctoken=784954501&forcesecure=1" tabindex="-1" style="font-family: tahoma, arial, sans-serif; font-size: 13px; text-align: center; width: 1px; height: 1px; position: absolute; top: -100px;">
ShareThis Copy and Paste
- See more at: http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/#sthash.T70JUj6V.dpuf

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?

cleanupDaemonThreads (exec.cleanupDaemonThreads)

 Wether to interrupt/join and possibly stop the daemon threads upon
 quitting.  If this is false, maven does nothing about the daemon threads.
 When maven has no more work to do, the VM will normally terminate any
 remaining daemon threads.
 In certain cases (in particular if maven is embedded), you might need to
 keep this enabled to make sure threads are properly cleaned up to ensure
 they don't interfere with subsequent activity. In that case, see
 daemonThreadJoinTimeout and stopUnresponsiveDaemonThreads for further
 tuning.

commandlineArgs (exec.args)

 Arguments for the executed program

daemonThreadJoinTimeout (exec.daemonThreadJoinTimeout, Default: 15000)

 This defines the number of milliseconds to wait for daemon threads to quit
 following their interruption. This is only taken into account if
 cleanupDaemonThreads is true. A value <=0 means to not timeout (i.e. wait
 indefinitely for threads to finish). Following a timeout, a warning will
 be logged. Note: properly coded threads should terminate upon interruption
 but some threads may prove problematic: as the VM does interrupt daemon
 threads, some code may not have been written to handle interruption
 properly. For example java.util.Timer is known to not handle interruptions
 in JDK <= 1.6. So it is not possible for us to infinitely wait by default
 otherwise maven could hang. A sensible default value has been chosen, but
 this default value may change in the future based on user feedback.

executableDependency

 If provided the ExecutableDependency identifies which of the plugin
 dependencies contains the executable class. This will have the affect of
 only including plugin dependencies required by the identified
 ExecutableDependency.
 If includeProjectDependencies is set to true, all of the project
 dependencies will be included on the executable's classpath. Whether a
 particular project dependency is a dependency of the identified
 ExecutableDependency will be irrelevant to its inclusion in the classpath.

includePluginDependencies (exec.includePluginDependencies, Default: false)

 Indicates if this plugin's dependencies should be used when executing the
 main class. This is useful when project dependencies are not appropriate. Using
 only the plugin dependencies can be particularly useful when the project is not
 a java project. For example a mvn project using the csharp plugins only expects
 to see dotnet libraries as dependencies.

includeProjectDependencies (exec.includeProjectDependencies, Default: true)

 Indicates if the project dependencies should be used when executing the
 main class.

mainClass (exec.mainClass)

 The main class to execute.

sourceRoot (sourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled. Use this if your plugin generates source code.

stopUnresponsiveDaemonThreads (exec.stopUnresponsiveDaemonThreads)

 Wether to call Thread.stop() following a timing out of waiting for an
 interrupted thread to finish. This is only taken into account if
 cleanupDaemonThreads is true and the daemonThreadJoinTimeout threshold has
 been reached for an uncooperative thread. If this is false, or if
 Thread.stop() fails to get the thread to stop, then a warning is logged
 and Maven will continue on while the affected threads (and related objects
 in memory) linger on. Consider setting this to true if you are invoking
 problematic code that you can't fix. An example is Timer which doesn't
 respond to interruption. To have Timer fixed, vote for this bug.

systemProperties

 A list of system properties to be passed. 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. See the user guide for more
 information.

testSourceRoot (testSourceRoot)

 This folder is added to the list of those folders containing source to be
 compiled for testing. Use this if your plugin generates test source code.

FAQ and Errors

Why do I get this error when specifying arguments to my main method:
view plain copy to clipboard print ?
jiafu1115
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
graphql-java-codegen-maven-plugin：graphql-java-codegen的Maven插件
02-04
graphql-java-codegen-maven-plugin就是这样一个插件，能够无缝集成到Maven构建流程中，自动根据GraphQL schema生成Java代码。 这个插件的主要作用包括： 1. **代码生成**：当你的GraphQL schema发生变化时，...
exec-maven-plugin：执行Maven插件
02-02
MojoHaus Exec Maven插件 这是 。 发行 确保gpg-agent正在运行。 执行mvn -B release:prepare release:perform 要发布网站，请执行以下操作： cd target/checkout mvn verify site site:stage scm-publish:...
Maven编译报错Cannot assign configuration entry 'includes' with value 'jacoco.exec'
FantasticXX的博客
09-23 2903
maven编译时报错： [ERROR] Failed to execute goal org.jacoco:jacoco-maven-plugin:0.8.4:merge (merge) on project mybundle-aggregator: Unable to parse configuration of mojo org.jacoco:jacoco-maven-plugin:0.8....
Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.ut
只为成功找方法 不为失败找借口
07-04 4423
maven命令出错：Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.util.Collections 我用的maven版本是3.6.0，据说3.5.4以上的版本很多都会有这个问题，我把版本降低到了3.5.0，问题完美解决 ...
禁止java exec_运行 mvn java:exec 如何避免 `IllegalThreadStateException`
weixin_33953395的博客
02-16 278
I would like to run a daemon thread which should start on maven package phase. This is what I have in pom.xml:org.codehaus.mojoexec-maven-plugin1.2.1packagejavacom.test.StartuptrueAnd here is the cont...
mvn编译报错-"Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of ty"
11-12 2316
参考：https://blog.csdn.net/Maxiao1204/article/details/94596387
运行 mvn java:exec 如何避免 `IllegalThreadStateException`
weixin_34318272的博客
12-25 599
2019独角兽企业重金招聘Python工程师标准>>> ...
apache-maven-3.9.4.zip
最新发布
08-04
apache-maven-3.9.4.zip压缩包内容： apache-maven-3.9.4-bin.tar.gz apache-maven-3.9.4-bin.zip apache-maven-3.9.4-src.tar.gz apache-maven-3.9.4-src.zip
Java-apache-maven-3.3.1.rar-安装包-kaic
04-30
Java_apache-maven-3.3.1.rar_安装包_kaic Java_apache-maven-3.3.1.rar_安装包_kaic Java_apache-maven-3.3.1.rar_安装包_kaic Java_apache-maven-3.3.1.rar_安装包_kaic Java_apache-maven-3.3.1.rar_安装包_kaic ...
apache-maven-3.8.4-bin.zip
12-07
Maven插件扩展了Maven的功能，例如`maven-compiler-plugin`用于编译Java代码，`maven-surefire-plugin`用于执行单元测试。每个插件都有多个目标(goal)，通过`mvn plugin:goal`命令执行。 **7. 本地仓库和远程仓库**...
maven 3.5.0 Cannot assign configuration entry 'pluginArtifacts' with value '${pl
08-09
Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.ut
Cannot assign value of type 'java.lang.String' to property 'file' of type 'org.apache.struts.upload.FormFile'
^_^-Beluga, ^_^-Stefli
01-06 4799
Exception：org.apache.commons.beanutils.ConversionException: Cannot assign value of type java.lang.String to property file of type org.apache.struts.upload.FormFile    at org.apache.struts.ac
maven中解决插件问题Failed org.codehaus.mojo:exec-maven-plugin
热门推荐
pcwlkpzc的博客
06-25 4万+
自己创建了一个maven工程，由于创建出来的maven工程中十分干净，什么都没有，我只要一运行就会报错：如下所示 Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (default-cli) 看到这个错误明显感觉到是插件的问题，自己在网上各种找解决方案，都是通过导入插件的方式来结局的，然后自己也尝试了一下，如下所示。 但是问题依旧没有解决。依旧报错。 最后自己在idea中使用骨架创建了一个quic...
flutter环境配置遇到的坑
wwp9527的博客
10-31 2万+
一、Flutter官方配置步骤 官方配置：https://flutterchina.club/setup-windows/ 1、未翻墙的电脑先配置临时镜像 就是在环境变量里配置下面两组键值对 PUB_HOSTED_URL = https://pub.flutter-io.cn FLUTTER_STORAGE_BASE_URL = https://storage.flutter-io.cn ...
用Maven跑Java main的3种方法
Elena专栏
01-28 7407
概述Maven exec plugin可以使我们运行自己工程的Java类的main方法，并在classpath里自动包含工程的dependencies。本文用示例代码展示了使用maven exec plugin来运行java main方法的3种方法。1) 在命令行（Command line）运行用这种方式运行的话，并没有在某个maven phase中，所以你首先需要compile（编译）一下代码。
maven实战常见错误与解决方法
Shao_win的专栏
03-18 9721
运行 mvn archetype:create -DgroupId=primary.simpleWeb \ -DartifactId=myWeb \ -DarchetypeArtifactId=maven-archetype-webapp \ -Dversion=1.0错误：The goal you specified requires a project to execute but there
解决vscode的报错：Java 11 or more recent is required to run the Java extension
無業䢟民的博客
09-17 6526
解决Java 11 or more recent is required to run the Java extension. Please download and install a recent JDK. 的问题 About the Java 11 requirement The Eclipse Platform has decided to require Java 11 as the minimum requirement for its September 2020 release. See h
分派任务时并不触发Assign Message Plugin
weixin_30542079的博客
07-05 112
问题描述：创建一个任务记录，然后更改任务负责人(进行记录分派)，Debug后发现并不触发assign message plugin。assign messageplugin注册情况如下图:问题解决方法：在对Activity（包括task, appointment, phonecall, email,letter etc)做Assign的时候MSCRM4.0实际...
解决IDEA启动时报错：Java 1.8 or later is required.
zgrjkflmkyc的专栏
12-07 7939
ubuntu下安装了jre7和jre8，当使用update-alternatives --config java将默认的jre设置为jre7后，启动idea报错：*** Java 1.8 or later is required. 可以使用update-alternatives --config java再将默认的jre设置为jre8, 但我的java工程需要在jdk7的环境下编译运行。 经测
XXL-JOB分布式任务调度平台：Java安装与部署指南
"java 实现xxl-job安装与部署" XXL-JOB是一个广泛使用的分布式任务调度平台，旨在提供快速开发、简单学习、轻量级且易于扩展的解决方案。该平台的核心特点是支持通过Web界面轻松管理任务，具备动态调度、高可用性...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值