[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.hibernate:hibernate-core:jar:4.0.0.FINAL
...
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
spring-milestone (http://maven.springframework.org/milestone),
Hibernate (http://repository.jboss.org/nexus/content/groups/public/)
But the same pom and repositories/dependencies work fine on my local dev build.
Jenkins is on an ubuntu box, all the other dependencies have worked fine. My java home is set to /usr/lib/jvm/java-7-openjdk-i386 and I have updated to latest version of Jenkins, in the hope it may fix problem.
My resolv.conf looks like this (i edited it using the resolvconf package)
GNU nano 2.2.6 File: /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 8.8.8.8
I am using the jboss repository to download the new hibernate jar, it is defined like so in the POM :
<repository>
<id>Hibernate</id>
<name>JBoss Hibernate repository</name>
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
</repository>
and I also get a warning from maven/jenkins :
[WARNING]
************ WARNING ************
This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.
LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement: org.apache.maven.ConfigurationInterpolator
NOTE: This seems to be a third-party Maven derivative you are using. If so, please
notify the developers for this derivative project of the problem. The Apache Maven team is not
responsible for maintaining the integrity of third-party component overrides.
It looks like you are using the wrong case in the ‘FINAL’ part of your version numbering.
Try
Although I don’t really know why it already worked locally. Maybe it’s the windows case insensitive file system and you already have the artifact cached from an other project …