-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
At least from Hudson 1.104 on including 1.106-SNAPSHOT (as of 4 May 2007)
Steps to reproduce:
1. c:\temp\hudson\> java -jar hudson.war
2. Configure system with
master = 0 executors
client1 = at least 1 executor fs root = c:\temp\hudson1
Maven 2.0.5
3. Start client1 via JNLP
4. Add Maven2 build job
The main job will build, the modules will hang with the following build log:
Building remotely on client1
$ java -cp "c:\temp\hudson1\maven-agent.jar;C:\Program Files\Apache Software
Foundation\maven-2.0.5\core\boot\classworlds-1.1.jar" hudson.maven.agent.Main
"C:\Program Files\Apache Software Foundation\maven-2.0.5"
\computer\client1\jnlpJars\remoting.jar c:\temp\hudson1\maven-interceptor.jar
Exception in thread "main" java.lang.ClassNotFoundException:
hudson.remoting.Launcher
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at
org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195)
at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255)
at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274)
at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274)
at hudson.maven.agent.Main.main(Main.java:61)
at hudson.maven.agent.Main.main(Main.java:31)
FATAL: null