When Oracle changes the cookie name they use to check if you have agreed to the license agreement, it currently requires a core change to make this happen. It would be best if the JDKInstaller was its own plugin, so we can just update the plugin, and that will allow older Jenkins installs to upgrade, if necessary.

          [JENKINS-22367] Move JDKInstaller to a plugin

          Larry Shatzer, Jr. created issue -
          Larry Shatzer, Jr. made changes -
          Link New: This issue is related to JENKINS-22347 [ JENKINS-22347 ]

          Jesse Glick added a comment -

          Agreed.

          We should also consider adding an installer for the JRE, which can be gotten from java.com more easily, I think, and which would suffice for some purposes. Not compiling Java programs, obviously—unless you are using (say) a Maven project requesting the Eclipse compiler. But possibly enough to run many Ant/Maven/Gradle builds. And all that is needed for SSH Slaves and similar slave launchers, since you only need a JRE for the slave agent.

          Jesse Glick added a comment - Agreed. We should also consider adding an installer for the JRE, which can be gotten from java.com more easily, I think, and which would suffice for some purposes. Not compiling Java programs, obviously—unless you are using (say) a Maven project requesting the Eclipse compiler. But possibly enough to run many Ant/Maven/Gradle builds. And all that is needed for SSH Slaves and similar slave launchers, since you only need a JRE for the slave agent.
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-22462 [ JENKINS-22462 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-3963 [ JENKINS-3963 ]
          Oleg Nenashev made changes -
          Issue Type Original: Bug [ 1 ] New: New Feature [ 2 ]
          Jesse Glick made changes -
          Labels New: split-plugins-from-core

          Jesse Glick added a comment -

          Even better, move JDK itself to a plugin, converting AbstractProject.jdk to a BuildWrapper in that plugin, so that the whole system can be removed for people not doing Java development. The main compatibility concern is Java callers of AbstractProject.getJDK (search).

          Jesse Glick added a comment - Even better, move JDK itself to a plugin, converting AbstractProject.jdk to a BuildWrapper in that plugin, so that the whole system can be removed for people not doing Java development. The main compatibility concern is Java callers of AbstractProject.getJDK ( search ).
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 154458 ] New: JNJira + In-Review [ 178804 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-26462 [ JENKINS-26462 ]

            dnusbaum Devin Nusbaum
            lshatzer Larry Shatzer, Jr.
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: