I don't think my issue is fixed.
I unchecked the "Automatic Install" and installed j2sdk1.4.2_11 to
C:\j2sdk1.4.2_11.
If I set the "JAVA_HOME" environment variable on the Hudson server and I
configure a "Free Style Software Project", the build works fine.
But we want to install, if possible, automated, multipple JDK's on the server
to be able to test the builds with newer JDK's. For that, we need to change the
JAVA_HOME variable dynamically depending on the build job. That is why I try to
create the same job in a "multi-configuration project".
In the configuration of the project, under "confguration matrix" I tick the box
next to j2sdk1.4.2_11.
In the log file of the job, only three lines of text appear:
Started by user <UserName>
Starten van j2sdk1.4.2_11
j2sdk1.4.2_11 is still in the queue: Waiting for next available executor
So even without "Automatic Install" ticked, the job does not start to build.
Is this issue reproducible on your server using a non-multi-conf project?