System default JDK wrongly used if JDK is created first

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Unassigned
            Reporter:
            Kohsuke Kawaguchi
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: