Hi,

apparantly there is software that relies on the Oracle JDK registry keys to run (at least Launch4j does, see https://sourceforge.net/p/launch4j/feature-requests/103/)

As workaround the installer could also add these registry keys. The Zulu JDK installer already does it this way:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft]

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit]
"CurrentVersion"="1.8"

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.8]
"JavaHome"="C:\\Program Files\\Zulu\\zulu-8"
"MicroVersion"="0"

Currently, the project provides a stable build for OpenJDK 11 for ARM32 (Raspberry Pi) with the following Jenkins Job:
https://ci.adoptopenjdk.net/view/arm/job/openjdk11_build_arm32_linux/

We should consider to design a solution to package and publish on Debian:
https://wiki.debian.org/Java

Once the build, passes the different Test suites from:
https://github.com/AdoptOpenJDK/openjdk-tests/

Juan Antonio

It would be great is AdoptOpenJDK could also ship RPM binaries just as Oracle currently do for their JDK. Redhat-based distributions are very common deployment platforms and this would ease the transition for people used to getting their JDK RPMs directly form Oracle.

We should create start creating installers for our binaries. The installation process should be pretty simple but we need to consider a few things:

• how to handle updates
• where the binary will be stored on the system
• will the installer include the binary or download it (web based on offline)
• do we need to codesign our installers?
• what language to write the installer in?

The way I view the installer working is as follows:

1. the user clicks install and the tarball is downloaded to the temp folder.
2. the installer checks the checksum to confirm that the tarball is correct.
3. the binary is then extracted to an AdoptOpenJDK folder that exists somewhere on the system.
4. the installer then removes all versions of AdoptOpenJDK from the PATH and updates with the new version. (the JAVA_HOME variable is also updated at this point)

There are a few ways to go about making this installer, I have already looked at electron as a possibility but have got stuck when it comes to permanently storing the AdoptOpenJDK path in the PATH environment variable.

Any help/suggestions welcome!

Platform: Windows 10 v1903 (OS Build 18362.53)
Architecture: 64-bit
AdoptOpen version: JRE 8u212-b03 (installer version)
JVM: HotSpot

Joining a world in Minecraft 1.13.2 causes the system to blue screen. Yeah, I dunno either.

Steps to reproduce:

1. Download MultiMC development version (this is the launcher I used, this probably happens with the vanilla launcher too though)
2. Create an instance for 1.13.2 (this may happen with other versions, haven't tested)
3. Launch that instance
4. In that instance, create a new world
5. Wait until the "Joining world..." text appears
6. RIP Windows

BitRock installers include an auto-update tool.

This issue is to investigate whether the auto-updater is suitable for the project, and write the client and server metadata to represent our releases.

A quick read through the docs implies that the autoupdater has to be invoked by cron / task scheduler on a regular check for updates on some platforms.

Because of the dependency of adoptopenjdk-* to ca-certificates-java in debian they are installed at the same time. For some reason both cannot be installed at the same time because ca-certificates-java needs a ready installed java to execute java but ca-certificates-java seems to be installed first so there is no java executable yet.

We have to look how openjdk-8-jre-headless does the magic in the debian package. It seems that the problem is this:

setup_path()
{
    for jvm in java-7-openjdk-$arch java-7-openjdk \
               oracle-java7-jre-$arch oracle-java7-server-jre-$arch oracle-java7-jdk-$arch \
               java-8-openjdk-$arch java-8-openjdk \
               oracle-java8-jre-$arch oracle-java8-server-jre-$arch oracle-java8-jdk-$arch \
               java-9-openjdk-$arch java-9-openjdk \
               oracle-java9-jre-$arch oracle-java9-server-jre-$arch oracle-java9-jdk-$arch \
               java-10-openjdk-$arch java-10-openjdk \
               oracle-java10-jre-$arch oracle-java10-server-jre-$arch oracle-java10-jdk-$arch \
               java-11-openjdk-$arch java-11-openjdk \
               oracle-java11-jre-$arch oracle-java11-server-jre-$arch oracle-java11-jdk-$arch \
               java-12-openjdk-$arch java-12-openjdk \
               oracle-java12-jre-$arch oracle-java12-server-jre-$arch oracle-java12-jdk-$arch \
               java-13-openjdk-$arch java-13-openjdk \
               oracle-java13-jre-$arch oracle-java13-server-jre-$arch oracle-java13-jdk-$arch \
               java-14-openjdk-$arch java-14-openjdk \
               oracle-java14-jre-$arch oracle-java14-server-jre-$arch oracle-java14-jdk-$arch \
               java-15-openjdk-$arch java-15-openjdk \
               oracle-java15-jre-$arch oracle-java15-server-jre-$arch oracle-java15-jdk-$arch \
               java-16-openjdk-$arch java-16-openjdk \
               oracle-java16-jre-$arch oracle-java16-server-jre-$arch oracle-java16-jdk-$arch \
               java-17-openjdk-$arch java-17-openjdk \
               oracle-java17-jre-$arch oracle-java17-server-jre-$arch oracle-java17-jdk-$arch; do
        if [ -x /usr/lib/jvm/$jvm/bin/java ]; then
            export JAVA_HOME=/usr/lib/jvm/$jvm
            PATH=$JAVA_HOME/bin:$PATH
            break
        fi
    done
}

I think we could and should patch upstream to include also adoptopenjdk.

But for now i think we have to remove the dependency to ca-certificates-java.

Hi guys,

This is more a question than an issue, some of our customers start using AdoptOpen JDK in windows and they report some issue when loading a jar in our platform, after some debugging we realized that before uploading the UI (Javascript code) validate the mime type if present, we have some hardcoded mime type but the more common seems application/java-archive , we noticed the installer configure the mime type to be application/jar, giving the fact we were not taking that value into account we rejected the file.

My question is why you have choose application/jar I looked in different places to ser if this was some standard, or defined in IANA but I didnt find anything, as far as I know we use application/java-archive because at the time of the development was the most widthly used also I think tomcat define that mime type for jar files.

https://github.com/AdoptOpenJDK/openjdk-installer/blob/c7dc8f6c71a11bfdfbeef329ab951b66b393414b/wix/Main.hotspot.wxs#L127

Also I think about Java 7 and the method Files.probeContentType which I think the implementation is platform dependent so I am assuming (because I didnt test it) in this case will return the same value from the registry. Which could be ok but at the same type the installer could be breaking other apps.

Regards,
Luis

Need to rename some names so it is clear we are installing JDK or JRE.

Thought first we will have OpenJRE and OpenJDK, but I might me wrong. Waiting for feedback on OpenJRE name.

The current MSI installer has one problem I'm currently trying to identify. If I run setup it remembers from an older installation the folder and suggests to install version 11.0.0.28 to folder with version 10.0.2.13 or 8.0.181.13. Need to find the reason first. Every installer need to be independed and need to install to it's own version directory.

MSI setup is not ready for prime time with this issue. Just to let you know.

The MSI installer is capable to write some registriy keys in Windows, e.g.

HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment
CurrentVersion REG_SZ 1.8

I only can enable this feature when using the GUI-Installer of the MSI file. I'm searching for the command line switch to enable this feature. Is there any docu about the cmd line installation of AdoptOpenJDK?

This same issue exists for Mac OS X. With Oracle JDK/JRE, the jar is associated with "jar launcher.app" (15.0.1). This app will not launch an AdoptOpenJDK created JAR.

Originally posted by @todivefor in #32 (comment)

OS : Windows 10 Enterprise b1809
AdoptOpenJDK build: 1.8.0_202_b08 (x64) (installed via MSI installer)
Java software to run: SQLWorkbench (http://www.sql-workbench.net/, http://www.sql-workbench.eu/)

Launching JAR via double-click on JAR : sqlworkbench.jar - OK
Launching JAR with CLI: java -jar sqlworkbench.jar - OK
Launch via EXE : SQLWorkbenhc64.exe Error - No suitable Java version could found. Please make sure you hava 64-bit Java 8 installed

SQLWorkbench64.exe/SQLWorkbench.exe are launchers which are based on WinRun4J (http://winrun4j.sourceforge.net/). It appears this launcher doesn't detect
AdoptOpenJDK properly probably due to a missing registry entry.

Screenshot of the error:

The draft packages (deb/rpm) of AdoptOpenJDK bundle the entire JDK. This is size-wise a problem for people that want their Docker images to be as small as possible.

Current situation on CentOS 7 (it's the same on other distributions): adoptopenjdk-11-hotspot comes in at around 310 MB. java-11-openjdk-headless provided by CentOS 7 weighs around 38 MB. Two big drivers for this difference are lib/src.zip (~58 MB) and the jmods (~80 MB) which are only necessary if you want to produce custom images with jlink.

Big question: Do we want to address this problem or just tell the people to use jlink?

If we want to address this problem, I see two possible ways forward (maybe there are more):

1. Follow the path of the AdoptOpenJDK Docker images and produce slim packages of the JRE and JDK.
2. Split the AdoptOpenJDK Deb and RPM packages like the Linux distributions do (but not to the exact same extent), i.e. move lib/src.zip and the jmods into separate packages.

Option 1 should yield the biggest weight savings because we can aggressively remove things.

The under development MSI installers are presenting the the openjdk LICENSE as the End User License Agreement. When installing openjdk-openj9 builds, this should be the license from the appropriate extensions for OpenJDK8 for Eclipse OpenJ9 repository - e.g. https://github.com/ibmruntimes/openj9-openjdk-jdk8/blob/openj9/LICENSE (GPLv2 with Classpath Exception).
This is very similar to the openjdk LICENSE, but there are some differences.

Windows Installer XML Toolset Validator version 3.11.1.2318
Copyright (c) .NET Foundation and contributors. All rights reserved.

OpenJDK12-jdk_x64_windows_openj9-12.0.0.32.msi
smoke.exe : error SMOK0217 : Error executing ICE action 'ICE01'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
smoke.exe : error SMOK0217 : Error executing ICE action 'ICE02'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
smoke.exe : error SMOK0217 : Error executing ICE action 'ICE03'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
smoke.exe : error SMOK0217 : Error executing ICE action 'ICE04'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
smoke.exe : error SMOK0217 : Error executing ICE action 'ICE05'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
smoke.exe : error SMOK0217 : Error executing ICE action 'ICE06'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
smoke.exe : error SMOK0217 : Error executing ICE action 'ICE07'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
smoke.exe : error SMOK0216 : An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE08' Fatal error during installation
Failed to validate MSI
Build step 'Execute Windows batch command' marked build as failure

They have been temporarily disabled through #65.

Further investigation of why they are failing is required.

I'm using AdoptOpenJDK's MSI installer. For some reason, I don't have elevated privilege of the windows machine.

Is there any way (besides extracting ZIP by my own) to install it?

The AdoptOpenJDK msi installers currently

1. Set JAVA_HOME when installing the jdk, disabled by default
2. Set JRE_HOME when installing the jre, disabled by default

So far I have only been able to identify Tomcat as an application which uses JRE_HOME.

There are many applications which use JAVA_HOME, (including Tomcat if JRE_HOME is not set), but the AdoptOpenJDK jre installer does not offer this as an option.

One approach might be to offer setting both JRE_HOME and JAVA_HOME when installing the jre?

@alexhass - when you originally provided the msi installer code, what was the rationale behind the current JAVA_HOME and JRE_HOME options?

For reference, this is the behaviour of other installers taken from a thread by @douph1 in the installer slack channel:

Installer who propose to set JAVA_HOME :

• Azul Zulu : dont
• Java.com (JRE): dont
• Oracle.com (JDK): dont
• Liberica Bellsoft : dont
• Amazon Corretto : YES as an option ENABLED by default
• OJDK (RedHat) : YES as an option DISABLED by default
• AdoptOpenJDK (currently): YES as an option DISABLED by default

Installer who propose to set JRE_HOME

• AdoptOpenJDK (currently) : instead of JAVA_HOME if build is JRE not JDK (edited)

Upgrade package for fedora Version 30.

https://github.com/AdoptOpenJDK/openjdk-installer/blob/8933422f46560eff2f3a3445c33adc246584522a/linux/rpm/build.gradle#L71

It would be great if the AdoptOpenJDK install also include IcedTea-Web natively, to ease the transition from Oracle JRE for Java WebStart applications.

IcedTea-Web is developed by RedHat and works on Linux, Windows and possibly also on macOS.

I know the SDKMan folks really wanted to become a potential deployment mechanism for the binaries - http://sdkman.io/ - much discussion etc would be required.

openjdk8-openj9 Windows milestone 1 build fails in the create_installer_windows job with

mv OpenJDK8-jdk_x86-32_windows_openj9-8.0.212.01.msi OpenJDK8U-jdk_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi OpenJDK8U-jre_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi
mv: target 'OpenJDK8U-jre_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi' is not a directory
Build step 'Execute shell' marked build as failure

Looks like mv has three arguments instead of two?

See job: https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_windows/284/console

Hi,
Is it possible to produce a RPM for amazonlinux/amazonlinux2?

It should be very similar to the Centos / Redhat.

Relates to:
#26

There are msi installers on the AdoptOpenJDK release download page for jdk8 but not for jdk11.

Hi. I Am Considering using AdoptOpenJDK.
...But I thought that I decompressed the archive and fiddled with the system a bit, I asked this question.
Is it possible to install AdoptOpenJDK even if there is no OpenJDK file in the future?
Also, is there a mechanism to install even at Java runtime only?

The main READMe file does not link to the linux subdir readme file to describe how those installers are built.

Hello together,

I'm looking for an OpenJDK MSI package that specifically supports software deployment (GPO). Unfortunately the MSI package ,,OpenJDK8U-jre_x64_windows_hotspot_8u202b08" does not work. So far it can't be deployed via the GPO. Has one of you made experiences and provided such MSI packages already in companies? I had already tried to change parameters with .mst files. So far nothing had worked.

Currently, the MSI installed creates some registry keys to specify the JAVA_HOME for a specific version. It would be useful to have a CurrentVersion key at the HKLM\SOFTWARE$(var.ProductManufacturer)$(var.ProductCategory) level which tells what the current latest installed version (default version) of OpenJDK that is installed. Oracle Java does this (at least for version 8) and is very nice.

So, you may have something like this in the registry:

HLKM\
  Software\
    AdoptOpenJDK\
      JDK\
        - CurrentVersion=8.0.202.08
        8.0.202.08\
          MSI\
            -Path=C:\....

This would allow another MSI installer to interrogate what the latest version is.

There is nothing explaining how to build the installer.

I'm a member of the IBM Runtimes classes team in Hursley, and would like to contribute to AdoptOpenJDK. I have a particular interest in installers...

(Following Geraint's how to)

Hello,

I've tried to deploy the JRE with openj9. With Orca I've made a transform (but can't find anything to set the language) for our needs.

The downloaded file is OpenJDK8U-jre_x64_windows_openj9_8u212b03_openj9-0.14.0.msi and it install the JRE in chinese language.

How can I change the language to german or english?

br
Marc

It looks like AdoptOpenJDK offers downloads from its website of JDK releases, and also offers a Homebrew tap for command line installation. However, I haven't been able to find a PPA that provides releases of AdoptOpenJDK binaries. Does one already exist, and if not then how about creating one for easy installation on Ubuntu servers?

FWIW, this issue is probably dependent on https://github.com/AdoptOpenJDK/openjdk-build/issues/458, since it'd be difficult to have a PPA if AdoptOpenJDK isn't offered as a DEB first! ;)

We are looking to migrate away all products from Oracle Java to OpenJDK.

To be able to deploy OpenJDK and OpenJRE in enterprise we need MSI installers. Currently I only see a ZIP file as download.

Can you create an MSI setup, please?

(Moved to here as #684 was closed)

When you double-click on a JAR the application it contains doesn't launch.
This is different behavior compared to the Oracle JDK/JRE. With this version this works.

Tested on Windows 10 x64

@douph1 has been particularly useful helping us setup the MSI installers. Would be great to get him invited to the org so he can contribute further.

Can I get an approval please @AdoptOpenJDK/getopenjdk

Hi, I'm trying to install AdoptOpenJDK on Fedora 30, but the repo doesn't work.

I created with sudo the file /etc/yum.repos.d/adoptopenjdk.repo with this content:

[AdoptOpenJDK]
name=AdoptOpenJDK
baseurl=http://adoptopenjdk.jfrog.io/adoptopenjdk/rpm/fedora/30/$(uname -m)
enabled=1
gpgcheck=1
gpgkey=https://adoptopenjdk.jfrog.io/adoptopenjdk/api/gpg/key/public

When I execute "sudo dnf check-update" or try to install AdoptOpenJDK the system discards the repo and says it can't sync it.

I don't know what I'm doing bad. I think its a repository problem.

Workflow:
brew cask install openjdK

Expected:
Works analog to brew cask install java

Instead:
No official cask.

Further Information:

• Implementation started at https://github.com/AdoptOpenJDK/homebrew-openjdk - however, not as a cask and not included into the main branch
• Brew: https://brew.sh
• Formulas: http://brewformulas.org
• Discussion on how to install OpenJDK: https://discourse.brew.sh/t/how-to-install-openjdk-with-brew/712

Will be really useful to support Snap format. It's available on mutliple linux distros.
http://snapcraft.io/

This maybe need the classic approach as AdoptOpenJDK will be used by external projects and may need access to external files.
https://docs.snapcraft.io/snap-confinement/6233

Hi guys,

I have been asked to prepare a deployment package with AdoptOpenJDK in my company since we are looking for an alternative solution to the Oracle Java releases. The thing is I am not able to find the MSI file for the AdoptOpenJDK 8u202 as am willing to deploy this package through SCCM and automate everything as much as I can.

Another topic is how can I change the settings of the package. E.g: with Oracle Java I send a report with the settings I want to apply to the Java Package: "Check for Updates Automatically", "Security Levels", "Advanced settings", etc, etc. Then this is configured as default in the Java deployment package. But with the AdoptOpenJDK I not sure how to do this or at least know which settings are available.

Thanks for your support.

When installing the latest build, the previous versions aren't removed for the JRE.

For example, if JRE 8 Update 202 was installed and you upgrade to 212 it leaves the previous version installed as well.

Is there a command line in the MSI you can enable to auto remove previous builds during an upgrade?

I tested the RPM found at https://dl.bintray.com/adoptopenjdk/rpm-nightly/centos/7/x86_64/Packages/ and it works, but it pulls in some i686 dependencies, which is unexpected. As a test I replaced installing the OS provided JDK in a Dockerfile, which results in a final image of 180MB larger than installing the OS provided JDK.

AdoptOpenJDK

Installing:
 adoptopenjdk-11-hotspot    x86_64 11.0.2+9-1       /adoptopenjdk-11-hotspot-11.0.2+9-1.x86_64
                                                                          310 M
 dejavu-lgc-sans-fonts         noarch    2.33-6.el7            base       1.0 M
 dejavu-lgc-sans-mono-fonts    noarch    2.33-6.el7            base       359 k
 dejavu-lgc-serif-fonts        noarch    2.33-6.el7            base       639 k
 dejavu-sans-fonts             noarch    2.33-6.el7            base       1.4 M
 dejavu-sans-mono-fonts        noarch    2.33-6.el7            base       433 k
 dejavu-serif-fonts            noarch    2.33-6.el7            base       776 k
 fontconfig                    x86_64    2.13.0-4.3.el7        base       254 k
 nmap-ncat                     x86_64    2:6.40-16.el7         base       206 k
 which                         x86_64    2.20-7.el7            base        41 k
Installing for dependencies:
 alsa-lib                      i686      1.1.6-2.el7           base       424 k
 dejavu-fonts-common           noarch    2.33-6.el7            base        64 k
 fontpackages-filesystem       noarch    1.44-8.el7            base       9.9 k
 freetype                      x86_64    2.8-12.el7_6.1        updates    380 k
 glibc                         i686      2.17-260.el7_6.4      updates    4.3 M
 libX11                        i686      1.6.5-2.el7           base       610 k
 libX11-common                 noarch    1.6.5-2.el7           base       164 k
 libXau                        i686      1.0.8-2.1.el7         base        29 k
 libXext                       i686      1.3.3-3.el7           base        39 k
 libXi                         i686      1.7.9-1.el7           base        40 k
 libXrender                    i686      0.9.10-1.el7          base        25 k
 libXtst                       i686      1.2.3-1.el7           base        20 k
 libpcap                       x86_64    14:1.5.3-11.el7       base       138 k
 libpng                        x86_64    2:1.5.13-7.el7_2      base       213 k
 libxcb                        i686      1.13-1.el7            base       230 k
 nss-softokn-freebl            i686      3.36.0-5.el7_5        base       211 k
 zlib                          i686      1.2.7-18.el7          base        91 k
Updating for dependencies:
 glibc                         x86_64    2.17-260.el7_6.4      updates    3.7 M
 glibc-common                  x86_64    2.17-260.el7_6.4      updates     12 M

CentOS Provided

Installing:
 dejavu-lgc-sans-fonts         noarch    2.33-6.el7            base       1.0 M
 dejavu-lgc-sans-mono-fonts    noarch    2.33-6.el7            base       359 k
 dejavu-lgc-serif-fonts        noarch    2.33-6.el7            base       639 k
 dejavu-sans-fonts             noarch    2.33-6.el7            base       1.4 M
 dejavu-sans-mono-fonts        noarch    2.33-6.el7            base       433 k
 dejavu-serif-fonts            noarch    2.33-6.el7            base       776 k
 fontconfig                    x86_64    2.13.0-4.3.el7        base       254 k
 java-11-openjdk-headless      x86_64    1:11.0.3.7-0.el7_6    updates     38 M
 nmap-ncat                     x86_64    2:6.40-16.el7         base       206 k
 which                         x86_64    2.20-7.el7            base        41 k
Installing for dependencies:
 alsa-lib                      x86_64    1.1.6-2.el7           base       424 k
 copy-jdk-configs              noarch    3.3-10.el7_5          base        21 k
 dejavu-fonts-common           noarch    2.33-6.el7            base        64 k
 fontpackages-filesystem       noarch    1.44-8.el7            base       9.9 k
 freetype                      x86_64    2.8-12.el7_6.1        updates    380 k
 javapackages-tools            noarch    3.4.1-11.el7          base        73 k
 libjpeg-turbo                 x86_64    1.2.90-6.el7          base       134 k
 libpcap                       x86_64    14:1.5.3-11.el7       base       138 k
 libpng                        x86_64    2:1.5.13-7.el7_2      base       213 k
 libxslt                       x86_64    1.1.28-5.el7          base       242 k
 lksctp-tools                  x86_64    1.0.17-2.el7          base        88 k
 python-javapackages           noarch    3.4.1-11.el7          base        31 k
 python-lxml                   x86_64    3.2.1-4.el7           base       758 k
 tzdata-java                   noarch    2019a-1.el7           updates    187 k

Originally posted by @stellirin in #25 (comment)

Both OpenJDK8U-jre_x64_windows_hotspot_8u202b08.msi
and OpenJDK8U-jre_x64_windows_openj9_8u202b08_openj9-0.12.1.msi
extract JRE in same directory
C:\Program Files\AdoptOpenJDK\jre-8.0.202.08
which lead to crash because of mix of JRE ..

To reproduce:
install openj9, then install hotspot ( keeping default directory proposed by the installer )

C:\Users\adminup>java -version
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000000000000, pid=4228, tid=0x0000000000001040
#
# JRE version:  (8.0_202-b08) (build )
# Java VM: OpenJDK 64-Bit Server VM (25.202-b08 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  0x0000000000000000
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\adminup\hs_err_pid4228.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

The installer must propose a directory name like that : [jre|jdk]-version-[hotspot|openj9]

Hi,

I've installed AdoptJDK 8 using pkg installer. Below is the name of the installer,
OpenJDK8U-jdk_x64_mac_hotspot_8u202b08 00-46-43-545.pkg

I want to install JDK 11 by uninstalling JDK 8, Could you please help me to uninstall OpenJDK 8 from my mac.

See adoptium/temurin-build#321 for the history

Currently icedtea-web is unconditionally added to all 64 bit msi installers. It should only be included in the jdk8 release.

Discussed with @pshipton

Please consider providing installers (I'm on Windows) that can update an existing JDK in place so that we don't have to manually install a new fix level, point applications at that new location, and manually uninstall the prior fix level.

For instance, I just installed jdk-8.0.212.03-openj9, pointed my Eclipse to use it, and then manually uninstalled jdk-8.0.202.08 (which also didn't even have the "-openj9" in the name either).

Further, having some way to even know there is an updated version available would be nice too. But I could see that being an entirely different feature.

Currently wix/Build.OpenJDK_generic.cmd generate always a new MSI ProductCode

FOR /F %%F IN ('POWERSHELL -COMMAND "$([guid]::NewGuid().ToString('b').ToUpper())"') DO (
  SET PRODUCT_UPGRADE_CODE=%%F
  ECHO PRODUCT_UPGRADE_CODE: !PRODUCT_UPGRADE_CODE!
)

This prevent MSI to upgrade.

See http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.html
https://docs.microsoft.com/fr-fr/windows/desktop/Msi/major-upgrades

Issues 32 and 34 were merged and closed. Those issues were for Windows. The same issue is true for MAC OS X. For Oracle JDK created JAR files, they are launched with "jar launcher.app" (15.0.1) found at /System/Library/CoreServices/Jar Launcher.app. Minor inconvenience, but a difference. I have found this with all AdoptOpenJDK releases on Mac OS X 10.14 and 10.13.