Question

I’m hosting ojdbc14.jar on my network nexus instance, but only local builds seem to pass.

I have this in my pom:

  <repositories>
    <repository>
        <releases>
            <enabled>true</enabled>
            <updatePolicy>always</updatePolicy>
            <checksumPolicy>warn</checksumPolicy>
        </releases>
        <id>thirdparty</id>
        <url>http://server/nexus/content/repositories/thirdparty</url>
    </repository>
  </repositories>

After completing removing ~/.m2/, a local mvn package will find ojdbc14.jar on nexus. My jenkins builds, conversely, consistently fail on this:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.csodehaus.mojo:sql-maven-plugin:1.3:execute (sql-ddl) on project mongo-dbunit: Execution 
sql-ddl of goal org.codehaus.mojo:sql-maven-plugin:1.3:execute failed: Plugin 
org.codehaus.mojo:sql-maven-plugin:1.3 or one of its dependencies could not be resolved: Could not find artifact com.oracle:ojdbc14:jar:10.2.0.4.0 in central 

Why?

(http://repo1.maven.org/maven2)

Answer 1

I’d check and make sure that the Maven settings are the same on both machines.

Jenkins by default uses the file in $HOME/.m2/settings.xml. It’s also possible for a Jenkins job to override this default.