-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Platform: HP, OS: Windows XP
When the option for which JDK to use for native m2 builds is set to "default"
and there is only one jdk configured in hudson the builds should use that jdk
not the jdk/jre of the container.
if there are more jdks' configured hudson should use the first one configured
at the system level for default.
- is related to
-
JENKINS-17373 Unconditionally display tool installation selector
-
- Open
-
-
JENKINS-10191 JDK selection is hidden even when a JDK is configured
-
- Open
-
-
JENKINS-12550 System default JDK wrongly used if JDK is created first
-
- Resolved
-
-
JENKINS-31217 No JDK named ‘null’ found in Jenkins 1.635
-
- Resolved
-
This inordinately long-standing issue is deeply insidious. We're currently in the process of mopping up the carnage caused by having merely added Java 7 to a Jenkins instance which previously only knew of Java 6 – an action that should be additive, and benign.
If this isn't going to be fixed any time soon, I would strongly recommend at least placing a giant disclaimer on the Jenkins Configuration page, detailing the peril of adding a second JDK. That would at least address the insidiousness, if not the bizarreness of the behaviour.