Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update AdoptOpenJDK 8 & 11, add upstream OpenJDK 8 & 11 (Linux & Windows) #171

Merged
merged 1 commit into from
Oct 29, 2019
Merged

Update AdoptOpenJDK 8 & 11, add upstream OpenJDK 8 & 11 (Linux & Windows) #171

merged 1 commit into from
Oct 29, 2019

Conversation

andrebrait
Copy link
Contributor

Note: Unfortunately, AdoptOpenJDK doesn't build upstream binaries for macOS

@ChangeSet(order = "209", id = "209-add_openjdk_8_0_232", author = "andrebrait")
def migrate209(implicit db: MongoDatabase) = {
List(
Version("java", "8.0.232-open", "https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u232-b09/OpenJDK8U-jdk_x64_linux_8u232b09.tar.gz", Linux64),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't really add adoptopenjdk builds as -open because this is reserved for reference implementation JDKs coming from http://jdk.java.net.

They aren't releasing any new versions of JDK8, and only seem to have new RIs for 11, 12 and 13 now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marc0der Although the URLs are from AdoptOpenJDK, these are actually binaries from upstream builds of the OpenJDK (see https://adoptopenjdk.net/upstream.html and AdoptOpenJDK/TSC#65)

So these are provided by AdoptOpenJDK on behalf of RedHat as builds of the reference implementation. We can find another name for them, if you want (perhaps redhat?) but these are technically the continuation of what is provided in http://jdk.java.net

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andrebrait Thanks for the explanation, it makes perfect sense now. I think keeping it under the -open label works perfectly in that case.

Going forward, would it be an idea for the AdoptOpenJDK project to start using our vendor API instead of using PRs? This could make things a lot easier than using a PR for each new release.

@marc0der marc0der merged commit e1897d2 into sdkman:master Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants