Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187

2013-06-11 Thread Mark Hobson
Fantastic! Thanks for that. Mark On 11 June 2013 21:33, Robert Scholte wrote: > After 272 failing builds finally FIXED! > > Jenkins build is back to normal : maven-plugins-ITs-m3-windows #273 > > Robert > > Op Sun, 09 Jun 2013 13:39:56 +0200 schreef Robert Scholte > : > > >> We're one step clo

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187

2013-06-11 Thread Robert Scholte
After 272 failing builds finally FIXED! Jenkins build is back to normal : maven-plugins-ITs-m3-windows #273 Robert Op Sun, 09 Jun 2013 13:39:56 +0200 schreef Robert Scholte : We're one step closer: Infra has added 2 options to the list of JDKs on the build-server. I've switched to JDK 1.5

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187

2013-06-09 Thread Robert Scholte
We're one step closer: Infra has added 2 options to the list of JDKs on the build-server. I've switched to JDK 1.5 and now the maven-javadoc-plugin succeeds. The job was executed with the following JVM Options: -Xmx768m -XX:MaxPermSize=128m should we change this? If yes, to what? Robert Op Sun

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187

2013-05-12 Thread Mark Hobson
Any ideas what the problem is with the Java installation on this slave? This build has been failing for as long as I remember, and every time it does it emails 18 people and counting. The secondary problem is the Maven Dependency Plugin tests failing with Java heap space, which then causes six ot

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187

2013-03-02 Thread Robert Scholte
I think I have to rephrase that. I just had a look at the logging. Now it is failing due to the following issue: Caused by: java.io.IOException: The environment variable JAVA_HOME=f:\hudson\tools\java\latest-1.5-64 doesn't exist or is not a valid directory. at org.apache.maven.plugin.jav

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187

2013-03-02 Thread Dennis Lundberg
AFAIK we only have one Windows slave. I think it would be better if we asked on builds@a.o to get the Javadoc tool to be installed properly on the existing slave. On 2013-03-01 21:07, Robert Scholte wrote: > Is it possible to add a javadoc label to the Windows-systems which do > have javadoc insta

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187

2013-03-01 Thread Robert Scholte
Is it possible to add a javadoc label to the Windows-systems which do have javadoc installed properly and add a restriction to this job to be sure it is executed on the right slave? Robert Op Fri, 01 Mar 2013 18:14:03 +0100 schreef Apache Jenkins Server : See