-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
I need to verify this, but I think what's happening is that when a Maven job (unverified on other job types), it sets the JDK to "(Default)", not null.
So later if a JDK is configured in the system config page, the job will not use it, but continue to use the "(Default)" JDK.
- is related to
-
JENKINS-10191 JDK selection is hidden even when a JDK is configured
- Open
-
JENKINS-755 Default JDK meaning in project options is confusing.
- Resolved