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

Java 11 #569

Closed
wants to merge 2 commits into from
Closed

Java 11 #569

wants to merge 2 commits into from

Conversation

rulle-io
Copy link
Contributor

Using more modern Java JDK & runtime (8 => 11).

Checklist for PR author(s)

  • Changes are covered by unit tests (no major decrease in code coverage %) and/or integration tests.
  • Ensure code formating (use mvn com.coveo:fmt-maven-plugin:format org.codehaus.mojo:license-maven-plugin:update-file-header)
  • Document any relevant additions/changes in the appropriate spot in javadocs/docs/README.

@rulle-io rulle-io linked an issue Jan 19, 2023 that may be closed by this pull request
@codecov
Copy link

codecov bot commented Jan 19, 2023

Codecov Report

Merging #569 (6a8ab22) into master (1668c7d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #569   +/-   ##
=========================================
  Coverage     91.47%   91.47%           
  Complexity      243      243           
=========================================
  Files            26       26           
  Lines           927      927           
  Branches         67       67           
=========================================
  Hits            848      848           
  Misses           52       52           
  Partials         27       27           

@labianchin
Copy link
Collaborator

What is the motivation for dropping support for Java 8?

Beam SDK, Dataflow, Flink, Spark, etc. still offer Java 8 support. Because of that I would expect DBeam to keep support Java 8 for a bit longer...

@rulle-io rulle-io changed the title Java11 Java 11 Jan 24, 2023
@rulle-io
Copy link
Contributor Author

Mainly following reasons:

  • ability to use new API in Java 11
  • Java 8 is 8 years old and unsupported anymore (Active support "Ended 9 months and 4 weeks ago (31 Mar 2022)" source)

I guess using JDK 11 in development and package library as Java 8 code is a way to combine usage of a supported JDK and widen possible interation space (not to exclude any applications still on Java 8)?

@labianchin
Copy link
Collaborator

Right. This project uses/requires Java 11 at build time. It builds targeting Java 8. So Java8 can be used at runtime.

Closing this. If there are other takes on it feel free to open follow up PR..

@labianchin labianchin closed this Apr 3, 2023
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.

Support for Java 11
2 participants