[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Robert Scholte closed an issue as Not A Bug Right, this is what's happening: You're executing exec:exec without a locked version in the pom.xml. So Maven will search for the latest version via internet or a repository manager if you have one. This seems to be the time consuming part. However, if you would have executed mvn org.codehaus.mojo:exec-maven-plugin:1.3.2:exec, then Maven knows which version of the plugin should be used. This way there's no need to visit the internet, since this version is already in your local repository. An advice: always lock plugin versions to ensure same results. Even though everybody is trying to stay backwards compatible, every now and then there's a release which does break it, resulting in broken builds. Mojo's Exec Maven Plugin / MEXEC-145 There is a 12 second delay after invoking exec:java or exec:exec Change By: Robert Scholte Resolution: Not A Bug Status: Reopened Closed Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Brett Ryan reopened an issue I disagree, the evidence does not correlate to that explanation. Note in all my logs that the delay occurs after the last line of maven output has been printed. There is no delay during the execution, execution occurs immediately, then there's a delay as evident by the maven time being short, but the time command being the lengthy one. Further investigation has shown that this is JDK8 related. As for your reasoning to lock in versions, sure for dependency and lifecycle plugins I agree, but this is not being used as part of a lifecycle. This plugin is the only one I have found to exhibit these symptoms. versions plugin for example does not, which requires more network traffic. Also note the delay is consistently reproducible and I have tried with a local nexus proxy and without. Mojo's Exec Maven Plugin / MEXEC-145 There is a 12 second delay after invoking exec:java or exec:exec Change By: Brett Ryan Status: Closed Reopened Resolution: Not A Bug Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Dan Tran commented on an issue Re: There is a 12 second delay after invoking exec:java or exec:exec Could you manage to get thread dump? 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
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Brett Ryan commented on an issue Re: There is a 12 second delay after invoking exec:java or exec:exec Here's the thread dump during the delay after execution has completed. Attaching to process ID 32478, please wait... Debugger attached successfully. Server compiler detected. JVM version is 25.20-b23 Deadlock Detection: No deadlocks found. Thread 19715: (state = BLOCKED) - java.lang.Thread.exit() @bci=0, line=754 (Interpreted frame) Thread 14595: (state = BLOCKED) - java.lang.Object.wait(long) @bci=0 (Interpreted frame) - java.lang.ref.ReferenceQueue.remove(long) @bci=44, line=142 (Compiled frame) - java.lang.ref.ReferenceQueue.remove() @bci=2, line=158 (Compiled frame) - java.lang.ref.Finalizer$FinalizerThread.run() @bci=36, line=209 (Interpreted frame) Thread 14083: (state = BLOCKED) - java.lang.Object.wait(long) @bci=0 (Interpreted frame) - java.lang.Object.wait() @bci=2, line=502 (Interpreted frame) - java.lang.ref.Reference$ReferenceHandler.run() @bci=36, line=157 (Interpreted frame) Thread 6403: (state = BLOCKED) - java.lang.Shutdown.halt0(int) @bci=0 (Interpreted frame) - java.lang.Shutdown.halt(int) @bci=7, line=139 (Interpreted frame) - java.lang.Shutdown.exit(int) @bci=99, line=213 (Interpreted frame) - java.lang.Runtime.exit(int) @bci=14, line=109 (Interpreted frame) - java.lang.System.exit(int) @bci=4, line=968 (Interpreted frame) - org.codehaus.plexus.classworlds.launcher.Launcher.main(java.lang.String[]) @bci=6, line=358 (Interpreted frame) 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 provid
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Kristian Rosenvold commented on an issue Re: There is a 12 second delay after invoking exec:java or exec:exec Can you make a complete sample project to reproduce this ? I find this issue interesting... 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
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Brett Ryan updated an issue Mojo's Exec Maven Plugin / MEXEC-145 There is a 12 second delay after invoking exec:java or exec:exec To reproduce use this pom with the following steps: Create new project directory Place pom.xml in director Within a JDK 8 environment execute time mvn clean package exec:exec Change By: Brett Ryan Attachment: pom.xml Add Comment 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
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title
Brett Ryan edited a comment on an issue
Re: There is a 12 second delay after invoking exec:java or exec:exec
To reproduce use this pom with the following steps:# Create new project directory# Place [^ pom.xml ] in director directory # Within a JDK 8 environment execute {{time mvn clean package exec:exec}}
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
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title
Brett Ryan edited a comment on an issue
Re: There is a 12 second delay after invoking exec:java or exec:exec
To reproduce use this pom with the following steps:# Create new project directory# Place [^pom.xml] in directory# Within a JDK 8 environment execute {{time mvn clean package exec:exec}} Have found that with a clean project {{mvn exec:exec}} alone is sufficient.
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
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Kristian Rosenvold commented on an issue Re: There is a 12 second delay after invoking exec:java or exec:exec Hmm. The pom doesnt contain a task to run ? I try mvn exec:exec -Dexec.executable=ls and I dont get any delay ? 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
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Brett Ryan commented on an issue Re: There is a 12 second delay after invoking exec:java or exec:exec What JDK? I have established problem is only prevelant with JDK8. Pom doesn't need any task, as I'm demonstrating the problem is present even when exec:exec is failing. Given the attached pom, placed in an empty directory, this is what you should get with JDK8 (I tried u20 on OSX and u05 on RHEL). (bryan@Bretts-MacBook-Pro)[~/Development/mvntest]$: mvn -version Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-12T06:58:10+10:00) Maven home: /opt/maven/default Java version: 1.8.0_20, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_20.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac" (bryan@Bretts-MacBook-Pro)[~/Development/mvntest]$: time mvn exec:exec [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building exec-test 1.0-SNAPSHOT [INFO] [INFO] [INFO] --- exec-maven-plugin:1.3.2-BR1:exec (default-cli) @ exec-test --- [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.402 s [INFO] Finished at: 2014-10-04T07:05:57+10:00 [INFO] Final Memory: 8M/245M [INFO] [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2-BR1:exec (default-cli) on project exec-test: The parameters 'executable' for goal org.codehaus.mojo:exec-maven-plugin:1.3.2-BR1:exec are missing or invalid -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginParameterException real 0m11.978s user 0m14.168s sys 0m0.170s Add Comment
[mojo-dev] [jira] (MBUILDNUM-123) Support for Accurev SCM
Title: Message Title Srinivas Nagesh commented on an issue Re: Support for Accurev SCM I found an issue in the above configuration. The above configuration is a part of a multi-module project. Since I specified inherited=false, the manifest of the child modules do not get the buildNumber. If I set it to true, then the plugin creates a buildNumber.properties file for each child module. This is not something I want to do as I would like the buildNumber to be managed from one location (buildNumber.properties at the parent). Any thoughts on how can I achieve this? Add Comment Mojo's Build Number Maven Plugin / MBUILDNUM-123 Support for Accurev SCM Could you please add support for Accurev SCM for the build number plugin? It appears that even after using the "revisionOnScmFailure" configuration, I keep running into "No such provider: 'accurev'." error. [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.3:create (default) on project ABC: Cannot get the revision informa... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) ---
[mojo-dev] [jira] (MEXEC-145) There is a 12 second delay after invoking exec:java or exec:exec
Title: Message Title Brett Ryan commented on an issue Re: There is a 12 second delay after invoking exec:java or exec:exec Jira instance doesn't allow reporter to update details, could someone update to specify this is JDK8 specific. 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
