Skip to content

Use full profile on JDK 10 builds #27884

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

Merged
merged 1 commit into from
Dec 20, 2017

Conversation

jasontedor
Copy link
Member

@jasontedor jasontedor commented Dec 19, 2017

JDK 10 has gone fully-modular. This means that:

  • when targeting JDK 8 with a JDK 10 compiler, we have to use the full profile
  • when targeting JDK 10 with a JDK 10 compiler, we have to use -add-modules java.base

Today we only target JDK 8 (our minimum compatibility version) so we need to change the compiler flags conditional on using a JDK 10 compiler. This commit does that.

Closes #27908

JDK 10 has gone fully-modular. This means that:
 - when targeting JDK 8 with a JDK 10 compiler, we have to use the full
   profile
 - when targeting JDK 10 with a JDK 10 compiler, we have to use
   -add-modules java.base

Today we only target JDK 8 (our minimum compatibility version) so we
need to change the compiler flags conditional on using a JDK 10
compiler. This commit does that.
@jasontedor jasontedor added :Delivery/Build Build or test infrastructure jdk10 labels Dec 19, 2017
@jasontedor jasontedor requested a review from rjernst December 19, 2017 02:37
@rjernst
Copy link
Member

rjernst commented Dec 19, 2017

Shouldn't we always be targeting java 8, since this is our minimum required version? Otherwise LGTM.

@jasontedor
Copy link
Member Author

Yes, we are still targeting JDK 8, there are no changes here for targeting JDK 10, I am only explaining the situation for completeness.

@rjernst
Copy link
Member

rjernst commented Dec 19, 2017

The reason for my comment is the conditional added here, based on the java version to select the profile. If compact profiles are going away, why don't we just remove specifying them altogether?

@jasontedor
Copy link
Member Author

The compact profile has benefits (we could be building smaller Docker images) and this will fold over to the modular world too. While we are not taking advantage of this, I think considering removal should be a separate change.

@jasontedor jasontedor merged commit 8bd7a19 into elastic:master Dec 20, 2017
jasontedor added a commit that referenced this pull request Dec 20, 2017
JDK 10 has gone fully-modular. This means that:
 - when targeting JDK 8 with a JDK 10 compiler, we have to use the full
   profile
 - when targeting JDK 10 with a JDK 10 compiler, we have to use
   -add-modules java.base

Today we only target JDK 8 (our minimum compatibility version) so we
need to change the compiler flags conditional on using a JDK 10
compiler. This commit does that.

Relates #27884
jasontedor added a commit that referenced this pull request Dec 20, 2017
JDK 10 has gone fully-modular. This means that:
 - when targeting JDK 8 with a JDK 10 compiler, we have to use the full
   profile
 - when targeting JDK 10 with a JDK 10 compiler, we have to use
   -add-modules java.base

Today we only target JDK 8 (our minimum compatibility version) so we
need to change the compiler flags conditional on using a JDK 10
compiler. This commit does that.

Relates #27884
jasontedor added a commit that referenced this pull request Dec 20, 2017
JDK 10 has gone fully-modular. This means that:
 - when targeting JDK 8 with a JDK 10 compiler, we have to use the full
   profile
 - when targeting JDK 10 with a JDK 10 compiler, we have to use
   -add-modules java.base

Today we only target JDK 8 (our minimum compatibility version) so we
need to change the compiler flags conditional on using a JDK 10
compiler. This commit does that.

Relates #27884
jasontedor added a commit that referenced this pull request Dec 20, 2017
JDK 10 has gone fully-modular. This means that:
 - when targeting JDK 8 with a JDK 10 compiler, we have to use the full
   profile
 - when targeting JDK 10 with a JDK 10 compiler, we have to use
   -add-modules java.base

Today we only target JDK 8 (our minimum compatibility version) so we
need to change the compiler flags conditional on using a JDK 10
compiler. This commit does that.

Relates #27884
@jasontedor jasontedor deleted the jdk-10-compact3 branch December 20, 2017 21:23
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure jdk10 Team:Delivery Meta label for Delivery team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI] Java 10: things are not available in profile 'compact3'
3 participants