Bug #1155
Hudson build of lib_client_java fails because maven can't find a dependency
100%
Description
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
No versions are present in the repository for the artifact with a range [1.5.6,)
org.slf4j:slf4j-api:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
Jibx Maven Repository (http://jibx.sourceforge.net/maven/),
sonatype.org (http://repository.sonatype.org/content/repositories/central)
Path to dependency:
1) org.dataone:d1_libclient_java:jar:0.5.2
2) net.sf.jsignature.io-tools:easystream:jar:1.2.9
History
#1 Updated by Dave Vieglais over 13 years ago
- % Done changed from 0 to 70
A temporary solution is to remove the local .m2 repository, and force maven to download new copies of dependencies. e.g.:
cd /usr/share/tomcat6/.m2
sudo mv repository repository_backup
Then execute the hudson jobs, starting at the base level (i.e. d1_common_java) which triggers a download of dependencies by maven and invokes the downstream builds.
This is not a satisfactory solution. A couple of potential alternatives to explore are listed in a (somewhat dated) article:
http://jlorenzen.blogspot.com/2008/07/maven-not-downloading-latest-snapshots.html
#2 Updated by Dave Vieglais over 13 years ago
- Status changed from New to Closed
- % Done changed from 70 to 100
Added a new Hudson project which purges the local repository, forcing a rebuild of everything once a day.
The Hudson project triggers a build of d1_common_java when complete.
Not a completely satisfactory solution, unless you're into nihilism.
ref: http://stackoverflow.com/questions/1308263/wiping-out-maven-local-repository-on-build-machine
