Posting the answer that is discussed in the comments section of the question. This solution worked for me! Thanks Andrew Logvinov cleanupDaemonThreads = false Something like this in the configuration tag <configuration> <mainClass>com.test.Startup</mainClass> <cleanupDaemonThreads>false</cleanupDaemonThreads> </configuration>
“configuration” must go outside “executions”, like this: <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.2.1</version> <executions> <execution> <goals> <goal>java</goal> </goals> </execution> </executions> <configuration> <mainClass>com.emilio.App</mainClass> </configuration> </plugin> </plugins>
I had a similar problem. As it turned out, I ran mvn clean package install Correct way is mvn clean install
I faced the same problem and figured it out. Shortly speaking, the class must be compiled before exec:java goal. (It surely works without test-compile phase if the class is already compiled by other user action. Note that Pascal Thivent, in his answer, invoked mvn test before exec:java.) $ mvn -Dexec.mainClass=… -Dexec.classpathScope=test test-compile exec:java You can … Read more
Goals in a multi-module project, when run from the parent, will run against all modules. I don’t think that’s what you want. You can try: mvn exec:java -pl module2 -Dexec.mainClass=MyMain That might work? More info: Running a specific Maven plugin goal from the command line in a sub-module of a multi-module reactor project However, I … Read more