Bug 750203

Summary: Maven randomly fails build (maven2) project
Product: [Fedora] Fedora Reporter: Pavel Alexeev <pahan>
Component: mavenAssignee: Stanislav Ochotnicky <sochotni>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: akurtako, dbhole, java-sig-commits, sochotni, yyang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-18 14:45:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pavel Alexeev 2011-10-31 10:51:06 UTC
Description of problem:
We use maven2 to our project. It consists from several modules. Maven build randomly failed build all project like:

$ mvn install -Dmaven.test.skip=true -Pcopy-dep
[skip]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:21.666s
[INFO] Finished at: Mon Oct 31 14:32:57 MSK 2011
[INFO] Final Memory: 21M/289M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project imus-esb-core: Could not resolve dependencies for project ru.antinform.ascug.esb.module:imus-esb-core:jar:1.4.6-SNAPSHOT: Could not find artifact ru.antinform.ascug.domain:ascug-domain:jar:tests:1.4.6-SNAPSHOT -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :imus-esb-core

When I rerun it as:
$ mvn install -Dmaven.test.skip=true -Pcopy-dep -rf :imus-esb-core
it is most possible imus-esb-core module wilol be built.
Wery strange, but resolve problems seams randoms on first glance.
Sequential rerun and continue allow me built full project, but it take very long time...


Version-Release number of selected component (if applicable):
$ rpm -qa 'maven*'
maven-release-2.2-3.fc16.noarch
maven-test-tools-1.2-9.fc16.noarch
maven-resources-plugin-2.5-4.fc16.noarch
maven-shared-file-management-1.2.2-18.fc16.noarch
maven-toolchain-2.2.1-28.fc16.noarch
maven-shared-invoker-2.0.12-18.fc16.noarch
maven-doxia-1.2-2.fc16.noarch
maven-parent-20-1.fc16.noarch
maven-deploy-plugin-2.7-1.fc16.noarch
maven-shared-reporting-api-3.0-18.fc16.noarch
maven-shared-15-18.fc16.noarch
maven-monitor-2.2.1-28.fc16.noarch
maven-javadoc-plugin-2.8-1.fc16.noarch
maven-surefire-provider-junit-2.9-1.fc16.noarch
maven-enforcer-plugin-1.0.1-2.fc16.noarch
maven-surefire-2.9-1.fc16.noarch
maven-artifact-manager-2.2.1-28.fc16.noarch
maven-shared-repository-builder-1.0-18.fc16.noarch
maven-install-plugin-2.3.1-3.fc16.noarch
maven-antrun-plugin-1.6-4.fc16.noarch
maven-project-2.2.1-28.fc16.noarch
maven-plugin-tools-model-2.7-1.fc16.noarch
maven-3.0.3-15.fc16.x86_64
maven-jxr-2.3-1.fc16.noarch
maven-compiler-plugin-2.3.2-4.fc16.noarch
maven-pmd-plugin-2.5-5.fc16.noarch
maven-surefire-plugin-2.9-1.fc16.noarch
maven-shared-monitor-1.0-18.fc16.noarch
maven-plugin-tools-beanshell-2.7-1.fc16.noarch
maven-dependency-plugin-2.3-1.fc16.noarch
maven2-2.2.1-28.fc16.noarch
maven-rar-plugin-2.2-6.fc16.noarch
maven-enforcer-rules-1.0.1-2.fc16.noarch
maven-shared-common-artifact-filters-1.3-18.fc16.noarch
maven-shared-dependency-tree-1.3-18.fc16.noarch
maven-project-info-reports-plugin-2.4-1.fc16.noarch
maven-plugin-build-helper-1.5-3.fc15.noarch
maven-archiver-2.4.1-7.fc16.noarch
maven-plugin-registry-2.2.1-28.fc16.noarch
maven-error-diagnostics-2.2.1-28.fc16.noarch
maven-wagon-1.0-0.3.b7.22.fc16.noarch
maven-plugin-testing-1.2-9.fc16.noarch
maven-eclipse-plugin-2.8-5.fc16.noarch
maven-stage-plugin-1.0-0.3.alpha2.fc16.noarch
maven-shared-reporting-impl-2.1-18.fc16.noarch
maven-shared-dependency-analyzer-1.2-18.fc16.noarch
maven-model-2.2.1-28.fc16.noarch
maven-plugin-tools-2.7-1.fc16.noarch
maven-war-plugin-2.1.1-4.fc16.noarch
maven-scm-1.5-1.fc16.noarch
maven2-common-poms-1.0-39.fc16.noarch
maven-release-manager-2.2-3.fc16.noarch
maven-doxia-sitetools-1.2-1.fc16.noarch
maven-enforcer-api-1.0.1-2.fc16.noarch
maven-clean-plugin-2.4.1-4.fc16.noarch
maven-surefire-report-plugin-2.9-1.fc16.noarch
maven-remote-resources-plugin-1.2.1-2.fc16.noarch
maven-assembly-plugin-2.2.1-3.fc16.noarch
maven-plugin-plugin-2.7-1.fc16.noarch
maven-jar-plugin-2.3.2-1.fc16.noarch
maven-enforcer-1.0.1-2.fc16.noarch
maven-shared-artifact-resolver-1.1-18.fc16.noarch
maven-profile-2.2.1-28.fc16.noarch
maven-plugin-tools-java-2.7-1.fc16.noarch
maven-one-plugin-1.2-6.fc16.noarch
maven-idea-plugin-2.2-5.fc16.noarch
maven-shared-model-converter-2.3-18.fc16.noarch
maven-plugin-tools-api-2.7-1.fc16.noarch
maven-plugin-bundle-2.0.0-10.fc16.noarch
maven-release-plugin-2.2-3.fc16.noarch
maven-source-plugin-2.1.2-6.fc16.noarch
maven-shared-downloader-1.2-18.fc16.noarch
maven-site-plugin-2.3-3.fc16.noarch
maven-plugin-jxr-2.3-1.fc16.noarch
maven-plugin-testing-harness-1.2-9.fc16.noarch
maven-filtering-1.0-4.fc16.noarch
maven-shared-io-1.2-18.fc16.noarch
maven-gpg-plugin-1.3-1.fc16.noarch
maven-doxia-tools-1.2-5.fc15.noarch

How reproducible:
Error reproduced each time, but concrete errors seams random.

Built on щзутовл 1.6:
# LANG=C alternatives --config java

There are 3 programs which provide 'java'.

  Selection    Command
-----------------------------------------------
 + 1           /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java
   2           /usr/lib/jvm/jre-1.7.0-openjdk.x86_64/bin/java
*  3           /usr/java/jdk1.7.0/jre/bin/java

Comment 1 Stanislav Ochotnicky 2011-10-31 13:18:41 UTC
Current F16 has Maven 3 as /usr/bin/mvn. If your project still needs maven2, you can use "mvn2" instead of "mvn". Be aware however we are doing our best to remove maven2 from distribution so that we only have to support the latest version. 

I am reassigning this bug to "maven" package (which contains maven 3) you have used.

I believe I've seen this behavior with maven 3.x before. Would it be possible to provide sources of the project? Or create a minimal project that fails? If not, I'll try to find other ways to do it.

Comment 2 Pavel Alexeev 2011-10-31 14:07:43 UTC
Hello, Stanislav.
Thank you very much for the such quick answer.
I had beleave what I even delete maven 3, so now endeed I see it not true and
mvn is maven3.

Project build when I use mvn2 command instead. But I also doubt my report
usefull for maven 3 when project had not adopted to it. From other side view -
by sequential restarts of build it is built almost all, so I make conclusion
what it should be drop in replacement.

Unfortunately for that project I strongly can't provide source, sorry. And as I
said before it failed randomly - I have no idea how reproduce it on some exact
part. Contrary it seams failed on things like cache or something similar. So,
you make close it then. But If I can be helpfull on some case - try run some
testst or provide additional info - please say.

Comment 3 Alexander Kurtakov 2011-11-18 14:45:56 UTC
Closing the bug as there is no obvious problem nor it can be reproduced in some open way.