You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "P. Ottlinger" <po...@apache.org> on 2016/05/22 21:37:08 UTC
Re: Build failed in Jenkins: Tamaya-Javadoc-Master #2
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
Re: Build failed in Jenkins: Tamaya-Javadoc-Master #2
Posted by "P. Ottlinger" <po...@apache.org>.
Am 24.05.2016 um 23:40 schrieb Oliver B. Fischer:
> Somehow the build is now working. Maybe because of my last changes? I
> don't know.
Looks like mere luck:
[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
:-)
Will be back tomorrow ...
The log contains strange errors as well, but not related to the codehaus
problem.
Phil
Re: Build failed in Jenkins: Tamaya-Javadoc-Master #2
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
Somehow the build is now working. Maybe because of my last changes? I
don't know.
Am 24.05.16 um 22:54 schrieb Oliver B. Fischer:
> Having a look at it I must admit that I don't know there it comes
> from. It must be something related to the configuration of Jenkins as
> it seems to work on our local machines.
>
> Am 24.05.16 um 20:55 schrieb Oliver B. Fischer:
>> I will have a look at it now.
>>
>> Am 23.05.16 um 00:09 schrieb John D. Ament:
>>
>
--
N Oliver B. Fischer
A Sch�nhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Build failed in Jenkins: Tamaya-Javadoc-Master #2
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
Having a look at it I must admit that I don't know there it comes from.
It must be something related to the configuration of Jenkins as it seems
to work on our local machines.
Am 24.05.16 um 20:55 schrieb Oliver B. Fischer:
> 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" <po...@apache.org> wrote:
>>
>
--
N Oliver B. Fischer
A Sch�nhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Build failed in Jenkins: Tamaya-Javadoc-Master #2
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
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" <po...@apache.org> 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 o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Build failed in Jenkins: Tamaya-Javadoc-Master #2
Posted by "John D. Ament" <jo...@apache.org>.
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" <po...@apache.org> 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
>