JDK Tool Plugin: Renaming to Oracle JDK Installer and next steps

[Oleg Nenashev]

Hi all,

I would like to provide some heads up about what's going on with the JDK Tool Plugin. This is a plugin which was detached from Jenkins 2.112, and this plugin DOES NOT provide a JDK Tool for Jenkins like many users may think. Actually it only provides an installer for Oracle JDK (Oracle Java SE Development Kit). The plugin has more than 200k installations, because it is considered as an implied dependency by plugins which target cores older than 2.112 (the majority of plugins ATM). 

The current state of the plugin is an issue, because Oracle changed the license for its JDK 11+ distributions, and they are not longer available for commercial use without Oracle license. We cannot integrate a crawler for Java 11 until it is resolved, because Jenkins users may be violating the license conditions otherwise. There were recent follow-ups like AdoptOpenJDK Plugin for Jenkins created by Mads Mohr Christensen (dev list thread). But we still need to do something about the "JDK Tool" Plugin to avoid confusion. JENKINS-57394 and JENKINS-57395 have been created to do so.

I have a proposal proposal to update the plugin state in 1.x baseline for Java 8 and then to cut a new 2.0 release to enable support of newer Java versions.

Version 1.3:

• The plugin is renamed to "Oracle Java SE Development Kit Installer" (PR #6). 
• Built-in and Internal Documentation updates (in  PR #6 and PR #5)
• License confirmation is marked as deprecated in the changelog

Version 1.4:

• Administrative monitor for the Tool installer usages. JENKINS-57395
• UI Control to accept the new Oracle license agreement. The previous agreement keeps working
• More improvements and copy-edits

Version 2.0:

• Users are forced to re-accept the license for the installer to keep using the installer if the new Oracle license has not been accepted yet
• The plugin is explicitly marked as incompatible with previous versions
• https://github.com/jenkins-infra/crawler/pull/82 is merged

There is no need to implement a full plan. I see 2 possible options:

• Option 1: We implement the full plan
• Option 2: We just keep the plugin on JDK 8 forever until full Oracle Java SE 8 Extended Support EoL in 2025. In such case we can stop at the version 1.4 without adding changes for the new license agreement. The plugin can be slowly deprecated once plugins really using this installer move to newer Jenkins versions.

What do you think about such options?

Best regards,

Oleg Nenashev

[Oleg Nenashev]

Meanwhile, I have released 1.3 which includes the documentation and Web UI patches: https://github.com/jenkinsci/jdk-tool-plugin/releases/tag/jdk-tool-1.3

[Mark Waite]

I prefer option 2 because I assume it is a little less work and still provides good results to Jenkins users.

I assume option 2 is not as certain as option 3 to assure that users have accepted the new Oracle license agreement before they download a new Oracle Java SE.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ef88a49b-451d-47e2-9877-5e261a7227c4%40googlegroups.com.

--

Thanks!

Mark Waite