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

2015-08-11 Thread Kogler Hannes (HKO 4530) (JIRA)

[ 
https://issues.apache.org/jira/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681665#comment-14681665
 ] 

Kogler Hannes (HKO 4530) commented on MNG-5315:
---

Dear Sir or Madam,

Thank you for your message. I am out of the office at the moment and will be 
back on Monday, 17th. August 2015.
I will reply to your e-mail as soon as possible when I return.

Please note that I will have limited access to my e-mail and your message will 
not be forwarded automatically.

For urgent issues may I refer you to my colleagues Michael Weichselbaumer (MWE) 
and Ronald Angerer (RAN).

Best regards

Hannes Kogler
Software Engineer

Registered Office | NTS New Technology Systems GmbH
Doernbacherstraße 126 | 4073 Wilhering | Austria
FN155693k | ATU42651803 | Court of Jurisdiction Linz



> Artifact resolution sporadically fails in parallel builds
> -
>
> Key: MNG-5315
> URL: https://issues.apache.org/jira/browse/MNG-5315
> Project: Maven
>  Issue Type: Bug
>  Components: Artifacts and Repositories
>Affects Versions: 3.0.4
>Reporter: Ivan 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(F

[jira] [Commented] (MRELEASE-426) There is no way to specify a branch/tag/revision when performing a release

2015-09-06 Thread Kogler Hannes (HKO 4530) (JIRA)

[ 
https://issues.apache.org/jira/browse/MRELEASE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733064#comment-14733064
 ] 

Kogler Hannes (HKO 4530) commented on MRELEASE-426:
---

Dear Sir or Madam,

Thank you for your message. I am out of the office at the moment and will be 
back on Thursday, 24th. September 2015.
I will reply to your e-mail as soon as possible when I return.

Please note that I will have limited access to my e-mail and your message will 
not be forwarded automatically.

For urgent issues may I refer you to my colleagues Michael Weichselbaumer (MWE) 
and Ronald Angerer (RAN).

Best regards

Hannes Kogler
Software Engineer

Registered Office | NTS New Technology Systems GmbH
Doernbacherstraße 126 | 4073 Wilhering | Austria
FN155693k | ATU42651803 | Court of Jurisdiction Linz



> There is no way to specify a branch/tag/revision when performing a release
> --
>
> Key: MRELEASE-426
> URL: https://issues.apache.org/jira/browse/MRELEASE-426
> Project: Maven Release Plugin
>  Issue Type: Improvement
>  Components: perform
>Affects Versions: 2.0-beta-8
> Environment: Maven2, CVSNT
>Reporter: Eric B
>
> When using the release-plugin with CVS, there does not seem to be any way to 
> specify a version & versionType to base the release on.
> The scm plugin allows to specify scmVersion, scmVersionType to pass this 
> information to the plugin, but when calling the release:perform goal, there 
> is no way to send this information to the scm plugin to checkout the files 
> from the appropriate branch/tag.
> Accordingly, it seems that with CVS, the only way to build a release is from 
> the latest sources in the HEAD; not extremely practical.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)