Set Java baseline to 11

[manusa]

Description

Part of #5778

Starting from version 7.0.0, the Fabric8 Kubernetes Client will require at minimum Java 11 to work.

Tasks

• Bump Maven Compiler source and target versions
  

  kubernetes-client/pom.xml

  Lines 174 to 175 in 50497aa

  	<maven.compiler.source>1.8</maven.compiler.source>
  	<maven.compiler.target>1.8</maven.compiler.target>

• Remove Maven compiler settings overrides
  

  kubernetes-client/junit/kube-api-test/pom.xml

  Lines 37 to 41 in 8622505

  	<properties>
  	<maven.compiler.release>11</maven.compiler.release>
  	<maven.compiler.target>11</maven.compiler.target>
  	<maven.compiler.source>11</maven.compiler.source>
  	</properties>

  
  

  kubernetes-client/httpclient-jdk/pom.xml

  Line 32 in 8622505

  <maven.compiler.release>11</maven.compiler.release>

  
  

  kubernetes-client/httpclient-jetty/pom.xml

  Line 32 in 8622505

  <maven.compiler.release>11</maven.compiler.release>

  
  

  kubernetes-client/httpclient-tests/pom.xml

  Line 32 in 8622505

  <maven.compiler.release>11</maven.compiler.release>

• Remove Java-11 specific profile in Maven pom.xml files and merge with defaults
  

  kubernetes-client/pom.xml

  Line 1509 in 50497aa

  <id>java-11</id>

  
  Pay attention to what was done in ci: release complete BOM #5190
• Remove 8 from build pipeline
  

  kubernetes-client/.github/workflows/build.yml

  Line 47 in 3c889e7

  java: [8,11,17,21]

• Change to 11 in e2e-tests pipeline
  

  kubernetes-client/.github/workflows/e2e-tests.yml

  Lines 55 to 58 in e3fa9c8

  	- name: Setup Java 8
  	uses: actions/setup-java@v4
  	with:
  	java-version: '8'

  
  

  kubernetes-client/.github/workflows/e2e-tests.yml

  Line 90 in e3fa9c8

  java-version: '8'

  
  

  kubernetes-client/.github/workflows/e2e-tests.yml

  Line 121 in e3fa9c8

  java-version: '8'

  
  

  kubernetes-client/.github/workflows/e2e-tests.yml

  Line 152 in e3fa9c8

  java-version: '8'

• Change to 11 in javadocs pipeline
  

  kubernetes-client/.github/workflows/javadocs.yml

  Lines 47 to 50 in 2540a22

  	- name: Setup Java 8
  	uses: actions/setup-java@v4
  	with:
  	java-version: '8'

• Simplify release and release-snapshots pipelines
  Everything can now be released in a single pass
  Pay attention to what was done in ci: release complete BOM #5190
• Add entry in migration guide

[andreaTP]

Now that we are at it:
https://www.oracle.com/java/technologies/java-se-support-roadmap.html

Java 11 is almost out of the support phase, would it make sense to bump directly to Java 17?

[manusa]

Now that we are at it: https://www.oracle.com/java/technologies/java-se-support-roadmap.html

Java 11 is almost out of the support phase, would it make sense to bump directly to Java 17?

Refer to #5778 (comment)

Most companies are going to provide commercial support for Java 11 well passed that date (just check the paid support column in your link).

The only reason I (personally) see to bump now is because it's becoming extremely difficult to maintain the project with such a low baseline, many of our dependencies have moved to Java 11.
Other than that, there are no clear advantages of upgrading the baseline past 11 and on the other hand there many disadvantages to do so.

[jorsol]

Now that we are at it: https://www.oracle.com/java/technologies/java-se-support-roadmap.html
Java 11 is almost out of the support phase, would it make sense to bump directly to Java 17?

Refer to #5778 (comment)

Most companies are going to provide commercial support for Java 11 well passed that date (just check the paid support column in your link).

This project should not be tied to companies that provide commercial support for Java 11... see my comment for a longer explanation: #5778 (comment)

But most importantly, if you check current ecosystem reports like the New Relic one, new Java versions are being adopted faster, is possible that Java 17 is more used than Java 11 right now... Spring 6 (Boot 3) and Quarkus 3.7 require Java 17 as the baseline, in other words, the ecosystem is starting to move faster.

The only reason I (personally) see to bump now is because it's becoming extremely difficult to maintain the project with such a low baseline, many of our dependencies have moved to Java 11. Other than that, there are no clear advantages of upgrading the baseline past 11 and on the other hand there many disadvantages to do so.

This is just my personal opinion, but I think there are more advantages of upgrading past 11 than disadvantages. There will be always trade-offs, so if you feel comfortable with Java 11 that's a good baseline too.

[manusa]

there are more advantages of upgrading past 11

Such as? (I'm referring specifically for this code-base and those advantages that would be impactful from a user's perspective)

[jorsol]

there are more advantages of upgrading past 11

Such as? (I'm referring specifically for this code-base and those advantages that would be impactful from a user's perspective)

Impactful from a user's perspective probably no, but advantages for the code-base maintainability could be, with Java 17 you have switch expression, text blocks, records, sealed classes, etc... all that would require some refactoring and the effort could not be worth it, but at least for new code or parts that can be refactored, there is an opportunity for that.

In any case, I don't mind keeping Java 11 as the baseline, I'm not a maintainer or even a casual contributor, and this discussion (that probably already happened) should be done with the team that maintains the project, so again, is just my personal preference, don't take it as advice or recommendation 😉 .

[manusa]

:) no worries

Impactful from a user's perspective probably no

I was just making sure that there wasn't anything else that could actually be interesting for users and that we missed out when weighing the pros/cons.

Personally, I need to keep multiple pet projects just to be able to test Java's new features 😅 Otherwise it's groundhog day in 2014 😭

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!