I will have a look at it now.
Am 23.05.16 um 00:09 schrieb John D. Ament:
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:
tamaya-code <<<
org.codehaus.mojo:findbugs-maven-plugin:3.0.1
http://nexus.codehaus.org/snapshots/org/apache/tamaya/buildconfigurations/0.3-incubating-SNAPSHOT/maven-metadata.xml
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
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
http://nexus.codehaus.org/snapshots/org/apache/tamaya/buildconfigurations/0.3-incubating-SNAPSHOT/buildconfigurations-0.3-incubating-SNAPSHOT.jar
Locally I'm able to launch 'clean javadoc:javadoc' with JDK8 and mvn 3.3.9.
Phil
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E [email protected]
S oliver.b.fischer
J [email protected]
X http://xing.to/obf
