[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec

[Brett Ryan (JIRA)]

Title: Message Title

Brett Ryan commented on an issue   Re: There is a 12 second delay after invoking exec:java or exec:exec A strange finding is that if I add the plugin to the build>plugins section the problem goes away. I discovered this by deciding to check out the source and building a custom build. All I had done was change the version identifier and added the plugin explicitly to my test project. To my surprise the problem went away, so I changed the version to 1.3.2 and again, surprisingly; no longer was the problem prevalent. So, maybe this bug is with maven itself? But why only is it noticeable against the mexec plugin? Maybe it's got to do with maven determining if all streams are closed? But again, why would it only be visible with implicit plugins, even though that plugins version is the same as defined. <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.3.2</version> </plugin> </plugins> </build> Add Comment   Mojo's Exec Maven Plugin / MEXEC-145 There is a 12 second delay after invoking exec:java or exec:exec Whenever I execute an exec goal there is always a 12 second delay after the execution of the exec goal has completed. This also occurs if I fail to provide exec:exec any required arguments. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email