[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2015-03-26 Thread Esteban Porcelli (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=365708#comment-365708
 ] 

Esteban Porcelli commented on MNG-5315:
---

This issue is marked with priority: minor

This is not a minor issue. We are using Maven in a large enterprise project.
The project takes one third the time to build using parallel builds (which is 
the reason for having parallel builds). 
But intermittent failures every other day are not acceptable as it requires 
manual intervention.

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor
 Fix For: Issues to be reviewed for 4.x

 Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch


 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2015-03-26 Thread Jason van Zyl (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=365716#comment-365716
 ] 

Jason van Zyl commented on MNG-5315:


If you are on a reasonably newer version of Maven you can try: 
http://takari.io/book/30-team-maven.html#concurrent-safe-local-repository

Or you can now use it as a core extension with Maven 3.3.1: 
http://takari.io/2015/03/19/core-extensions.html

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor
 Fix For: Issues to be reviewed for 4.x

 Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch


 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2014-02-18 Thread Edward J. Yoon (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=341670#comment-341670
 ] 

Edward J. Yoon commented on MNG-5315:
-

https://builds.apache.org/job/Hama-trunk/274/console

Is this the same issue?

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor
 Fix For: Issues to be reviewed for 4.x

 Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch


 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2014-02-18 Thread Edward J. Yoon (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=341670#comment-341670
 ] 

Edward J. Yoon edited comment on MNG-5315 at 2/18/14 4:30 PM:
--

https://builds.apache.org/job/Hama-trunk/274/console

Is this the same issue?


Oh, sorry. I've changed version of rat plugin.


was (Author: udanax):
https://builds.apache.org/job/Hama-trunk/274/console

Is this the same issue?

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor
 Fix For: Issues to be reviewed for 4.x

 Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch


 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2014-01-23 Thread Jason van Zyl (JIRA)

 [ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl updated MNG-5315:
---

Fix Version/s: Issues to be reviewed for 4.x

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor
 Fix For: Issues to be reviewed for 4.x

 Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch


 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: 
 The 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-10-11 Thread Stephen Evanchik (JIRA)

 [ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Evanchik updated MNG-5315:
--

Attachment: MNG-5315-3.1.2-SNAPSHOT.patch

Simple synchronization as proposed in this issue against 3.1.2-SNAPSHOT

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor
 Attachments: MNG-5315-3.1.2-SNAPSHOT.patch


 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve dependencies for project 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-10-11 Thread Stephen Evanchik (JIRA)

 [ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Evanchik updated MNG-5315:
--

Attachment: MNG-5315-3.0.x.patch

Patch suitable for the 3.0.x branch

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor
 Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch


 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: 
 The following 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-10-11 Thread Stephen Evanchik (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=334031#comment-334031
 ] 

Stephen Evanchik commented on MNG-5315:
---

Alternatively one can create a custom Component that adds this without 
modifying maven-core. Here is an example against 3.1.2-SNAPSHOT and a 3.0.x:

 https://github.com/evanchsa/maven-parallel-resolver.git

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor
 Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch


 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-09-03 Thread Sami Salonen (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=332278#comment-332278
 ] 

Sami Salonen commented on MNG-5315:
---

Thanks a lot Sandy for your solution.

We used to suffer from this very same problem on a daily basis. I applied your 
patch to both maven 3.0.5 and 3.1.0. Now, after one month and about 3000 builds 
later, not a single build has failed for this problem anymore. Perfect.

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-07-29 Thread Sandy McPherson (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=329729#comment-329729
 ] 

Sandy McPherson commented on MNG-5315:
--

My first fix was with a 3.1-SNAPSHOT from the beginning of June. I then went 
back and patched 3.0.5 as we didn't want to use a snapshot. The 3.1-SNAPSHOT I 
checked out a version from June 2 21:32:45 (last committer Arnaud Heritier). 
This was definitely still broken.

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-07-28 Thread Karthikeyan Kulasekaran (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=329716#comment-329716
 ] 

Karthikeyan Kulasekaran commented on MNG-5315:
--

Please fix this issue as well MNG-5252. This is related to MNG-5315

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: 
 The following artifacts could not 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-07-28 Thread Kristian Rosenvold (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=329727#comment-329727
 ] 

Kristian Rosenvold commented on MNG-5315:
-

Can you please re-test with maven 3.1.0 ? The root cause of this issue may be 
fixed there.

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: 
 The following 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-07-26 Thread Jason van Zyl (JIRA)

 [ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl reassigned MNG-5315:
--

Assignee: Jason van Zyl

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Assignee: Jason van Zyl
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: 
 The following artifacts could not be resolved: 
 commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-07-25 Thread Christoph Kutzinski (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=329469#comment-329469
 ] 

Christoph Kutzinski commented on MNG-5315:
--

Sandy, this sounds great - when will it be available in a release?

BTW: did I understand you correctly: you made it single-threaded and it became 
faster?

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve dependencies for project 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-07-25 Thread Sandy McPherson (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=329515#comment-329515
 ] 

Sandy McPherson commented on MNG-5315:
--

Making the parallel builds work gave us the performance increase. Only 
dependency resolution is restricted to one thread at a time, due to some race 
condition, which I didn't attempt to analyse in depth.

I don't know when it will be in a release, I am not part of the maven 
developers group. It is however straightforward to patch maven by downloading 
the source and adding the synchronize where I did.

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-06-07 Thread Sandy McPherson (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=326367#comment-326367
 ] 

Sandy McPherson edited comment on MNG-5315 at 6/7/13 2:21 PM:
--

After a few false starts I found a plausible solution. 

I Patched to only allow one thread at a time to do dependency resolution. I 
tried to do this with finer granularity (per artifact) but failed miserably due 
to the program structure. However the performance gain we have achieved in the 
builds we were targeting was one order of magnitude!

{code}
DefaultProjectDependenciesResolver

public DependencyResolutionResult resolve(
DependencyResolutionRequest request)
throws DependencyResolutionException {
long start = System.currentTimeMillis();
System.out.println(0  locking 
+DefaultProjectDependenciesResolver.class);
synchronized (DefaultProjectDependenciesResolver.class) {
System.out.println((System.currentTimeMillis()-start)+  locked 
+DefaultProjectDependenciesResolver.class);
RequestTrace trace = RequestTrace.newChild(null, request);
.
.
.
.
.
System.out.println((System.currentTimeMillis()-start)+  
unlocked +DefaultProjectDependenciesResolver.class);
return result;
}
{code}

Results are now

No failures so far. Massive speed improvements on larger builds with similar 
dependencies:

serial: 10-11m 
-T 1C  1.5m
-T 2C 1.25m
-T 3C nearly 1m


  was (Author: sandymcp):
After a few false starts I found a plausible solution. 

I Patched to only allow one thread at a time to do dependency resolution. I 
tried to do this with finer granularity (per artifact) but failed miserably due 
to the program structure. However the performance gain we have achieved in the 
builds we were targeting was one order of magnitude!

DefaultProjectDependenciesResolver

public DependencyResolutionResult resolve(
DependencyResolutionRequest request)
throws DependencyResolutionException {
long start = System.currentTimeMillis();
System.out.println(0  locking 
+DefaultProjectDependenciesResolver.class);
synchronized (DefaultProjectDependenciesResolver.class) {
System.out.println((System.currentTimeMillis()-start)+  locked 
+DefaultProjectDependenciesResolver.class);
RequestTrace trace = RequestTrace.newChild(null, request);
.
.
.
.
.
System.out.println((System.currentTimeMillis()-start)+  
unlocked +DefaultProjectDependenciesResolver.class);
return result;
}


Results are now

No failures so far. Massive speed improvements on larger builds with similar 
dependencies:

serial: 10-11m 
-T 1C  1.5m
-T 2C 1.25m
-T 3C nearly 1m

  
 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-06-07 Thread Sandy McPherson (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=326367#comment-326367
 ] 

Sandy McPherson commented on MNG-5315:
--

After a few false starts I found a plausible solution. 

I Patched to only allow one thread at a time to do dependency resolution. I 
tried to do this with finer granularity (per artifact) but failed miserably due 
to the program structure. However the performance gain we have achieved in the 
builds we were targeting was one order of magnitude!

DefaultProjectDependenciesResolver

public DependencyResolutionResult resolve(
DependencyResolutionRequest request)
throws DependencyResolutionException {
long start = System.currentTimeMillis();
System.out.println(0  locking 
+DefaultProjectDependenciesResolver.class);
synchronized (DefaultProjectDependenciesResolver.class) {
System.out.println((System.currentTimeMillis()-start)+  locked 
+DefaultProjectDependenciesResolver.class);
RequestTrace trace = RequestTrace.newChild(null, request);
.
.
.
.
.
System.out.println((System.currentTimeMillis()-start)+  
unlocked +DefaultProjectDependenciesResolver.class);
return result;
}


Results are now

No failures so far. Massive speed improvements on larger builds with similar 
dependencies:

serial: 10-11m 
-T 1C  1.5m
-T 2C 1.25m
-T 3C nearly 1m


 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-05-30 Thread Sandy McPherson (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=325915#comment-325915
 ] 

Sandy McPherson commented on MNG-5315:
--

We're also seeing this using Teamcity and Nexus. Which repository are you guys 
using? Could the root problem be Nexus related? Would appear that maven does 
not find the dependency in Nexus. We have a couple of Nexus repositories which 
are being searched. 

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2013-05-30 Thread Ivan S. Dubrov (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=325932#comment-325932
 ] 

Ivan S. Dubrov commented on MNG-5315:
-

No, it's not repository related. The issue never happens in a single-threaded 
build. It looks like it happens due to the race-condition between two threads 
trying to download the same artifact at the same time. Also, even though build 
is failed the dependency is actually downloaded into the local repository (so 
you can see it there after the build fails).

Something like (just speculating):

1) first thread looks into the local repository, nothing there, goes to the 
remote repository
2) first thread downloads remote dependency, but does not update 
_maven.repositories yet.
3) second thread looks into the local repository, sees the dependency, but 
_maven.repositories does not contain remote repository id!
4) second thread fails with Could not resolve dependencies, since it thinks 
dependency is not available from the remote repository.
5) first thread updates _maven.repositories. Next time build is invoked, 
dependency is used from the local repository.

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2012-11-02 Thread Christoph Kutzinski (JIRA)

[ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=312774#comment-312774
 ] 

Christoph Kutzinski commented on MNG-5315:
--

We're seeing similar errors in our CI environment (Jenkins) quite frequently - 
i.e. several times a day.

This causes major manual effort to determine the cause of the failure, restart 
the build and wait

 Artifact resolution sporadically fails in parallel builds
 -

 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Priority: Minor

 Artifact resolution can fail during the parallel build if it was downloaded 
 during the same session.
 Scenario:
 1) Delete the whole Maven local repository.
 2) Run build mvn compile -T1.5C
 3) Build fails (see log extracts below)
 4) If I run build again, it succeeds.
 It seems like the problem is due to two thread trying to resolve same 
 artifact concurrently. This problem never happens once I have all 
 dependencies cached in the local repository.
 Extracts from the log output:
 {noformat}Downloading: 
 http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
  12444/13937 KB ...
 ...
 [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
 already updated during this session.
 [DEBUG] Skipped remote update check for 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
 session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, 
 already updated during this session.
 [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
 already updated during this session.
 ...
 [ERROR] Failed to execute goal on project util: Could not resolve 
 dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
 following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced - [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal on project util: Could not resolve dependencies for project 
 com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not 
 be resolved: commons-cli:commons-cli:jar:1.2, 
 com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, 
 org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to 
 find commons-cli:commons-cli:jar:1.2 in 
 http://nexus/content/repositories/thirdparty was cached in the local 
 repository, resolution will not be reattempted until the update interval of 
 gw.thirdparty has elapsed or updates are forced
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
 at 
 org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
 at 
 org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
 resolve 

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2012-10-22 Thread Herve Boutemy (JIRA)

 [ 
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MNG-5315:
---

Description: 
Artifact resolution can fail during the parallel build if it was downloaded 
during the same session.

Scenario:

1) Delete the whole Maven local repository.
2) Run build mvn compile -T1.5C
3) Build fails (see log extracts below)
4) If I run build again, it succeeds.

It seems like the problem is due to two thread trying to resolve same artifact 
concurrently. This problem never happens once I have all dependencies cached in 
the local repository.

Extracts from the log output:

{noformat}Downloading: 
http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
 12444/13937 KB ...
...
[DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
already updated during this session.
[DEBUG] Skipped remote update check for 
com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
session.
[DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, already 
updated during this session.
[DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
already updated during this session.
...
[ERROR] Failed to execute goal on project util: Could not resolve dependencies 
for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts 
could not be resolved: commons-cli:commons-cli:jar:1.2, 
com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, org.slf4j:slf4j-api:jar:1.6.4, 
org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to find 
commons-cli:commons-cli:jar:1.2 in http://nexus/content/repositories/thirdparty 
was cached in the local repository, resolution will not be reattempted until 
the update interval of gw.thirdparty has elapsed or updates are forced - [Help 
1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
on project util: Could not resolve dependencies for project 
com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not be 
resolved: commons-cli:commons-cli:jar:1.2, 
com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, org.slf4j:slf4j-api:jar:1.6.4, 
org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to find 
commons-cli:commons-cli:jar:1.2 in http://nexus/content/repositories/thirdparty 
was cached in the local repository, resolution will not be reattempted until 
the update interval of gw.thirdparty has elapsed or updates are forced
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
at 
org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
resolve dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, org.slf4j:slf4j-api:jar:1.6.4, 
org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to find 
commons-cli:commons-cli:jar:1.2 in http://nexus/content/repositories/thirdparty 
was cached in the local repository, resolution will not be reattempted until 
the update interval of gw.thirdparty has elapsed or updates are forced
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)

[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds

2012-07-17 Thread Ivan S. Dubrov (JIRA)
Ivan S. Dubrov created MNG-5315:
---

 Summary: Artifact resolution sporadically fails in parallel builds
 Key: MNG-5315
 URL: https://jira.codehaus.org/browse/MNG-5315
 Project: Maven 2  3
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 3.0.4
Reporter: Ivan S. Dubrov
Priority: Minor


Artifact resolution can fail during the parallel build if it was downloaded 
during the same session.

Scenario:

1) Delete the whole Maven local repository.
2) Run build mvn compile -T1.5C
3) Build fails (see log extracts below)
4) If I run build again, it succeeds.

It seems like the problem is due to two thread trying to resolve same artifact 
concurrently. This problem never happens once I have all dependencies cached in 
the local repository.

Extracts from the log output:

Downloading: 
http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
 12444/13937 KB ...
...
[DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2, 
already updated during this session.
[DEBUG] Skipped remote update check for 
com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this 
session.
[DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4, already 
updated during this session.
[DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4, 
already updated during this session.
...
[ERROR] Failed to execute goal on project util: Could not resolve dependencies 
for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts 
could not be resolved: commons-cli:commons-cli:jar:1.2, 
com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, org.slf4j:slf4j-api:jar:1.6.4, 
org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to find 
commons-cli:commons-cli:jar:1.2 in http://nexus/content/repositories/thirdparty 
was cached in the local repository, resolution will not be reattempted until 
the update interval of gw.thirdparty has elapsed or updates are forced - [Help 
1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
on project util: Could not resolve dependencies for project 
com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not be 
resolved: commons-cli:commons-cli:jar:1.2, 
com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, org.slf4j:slf4j-api:jar:1.6.4, 
org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to find 
commons-cli:commons-cli:jar:1.2 in http://nexus/content/repositories/thirdparty 
was cached in the local repository, resolution will not be reattempted until 
the update interval of gw.thirdparty has elapsed or updates are forced
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
at 
org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
resolve dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The 
following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2, 
com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, org.slf4j:slf4j-api:jar:1.6.4, 
org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to find 
commons-cli:commons-cli:jar:1.2 in http://nexus/content/repositories/thirdparty 
was cached in the local repository, resolution will not be reattempted until 
the update interval of gw.thirdparty has elapsed or updates are forced
at