Seems like a config issue in our project. Codehaus shutdown a little while ago but our javadocs still require it? On May 22, 2016 17:37, "P. Ottlinger" <[email protected]> wrote:
> Hi, > > does anyone know if that is a problem with the build agents or a > configuration problem? > > Am 22.05.2016 um 23:23 schrieb Apache Jenkins Server: > > [INFO] <<< maven-javadoc-plugin:2.9.1:javadoc < generate-sources @ > tamaya-code <<< > > [INFO] configuring report plugin org.apache.rat:apache-rat-plugin:0.11 > > [INFO] configuring report plugin > org.codehaus.mojo:findbugs-maven-plugin:3.0.1 > > [INFO] Downloading: > http://nexus.codehaus.org/snapshots/org/apache/tamaya/buildconfigurations/0.3-incubating-SNAPSHOT/maven-metadata.xml > > [WARNING] Could not transfer metadata > org.apache.tamaya:buildconfigurations:0.3-incubating-SNAPSHOT/maven-metadata.xml > from/to codehaus-snapshots (http://nexus.codehaus.org/snapshots/): > nexus.codehaus.org: Name or service not known > > [WARNING] Failure to transfer > org.apache.tamaya:buildconfigurations:0.3-incubating-SNAPSHOT/maven-metadata.xml > from http://nexus.codehaus.org/snapshots/ was cached in the local > repository, resolution will not be reattempted until the update interval of > codehaus-snapshots has elapsed or updates are forced. Original error: Could > not transfer metadata > org.apache.tamaya:buildconfigurations:0.3-incubating-SNAPSHOT/maven-metadata.xml > from/to codehaus-snapshots (http://nexus.codehaus.org/snapshots/): > nexus.codehaus.org: Name or service not known > > [INFO] Downloading: > http://nexus.codehaus.org/snapshots/org/apache/tamaya/buildconfigurations/0.3-incubating-SNAPSHOT/buildconfigurations-0.3-incubating-SNAPSHOT.jar > > [FINDBUGS] No report found for mojo site > > Locally I'm able to launch 'clean javadoc:javadoc' with JDK8 and mvn 3.3.9. > > Phil >
