-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: All
When slave configuration is changed with a new location for the workspace
selected, but slave not restarted, m2 project fails with an error like:
[common] $ /opt/jdk1.6.0_03/bin/java -cp
/mnt/hudson_workspace/maven-agent.jar:/opt/maven-2.0.6/boot/classworlds-1.1.jar
hudson.maven.agent.Main /opt/maven-2.0.6
/services/hudson/hudson_release/WEB-INF/slave.jar
/mnt/hudson_workspace/maven-interceptor.jar
Exception in thread "main" java.lang.NoClassDefFoundError: hudson/maven/agent/Main
That's because both maven jars normally copied to the WS directory on slave
startup are missing from the new directory.
So when workspace changes in slave configuration, hudson should take care to
perform the same operations over the new workspace like it does the initial one.