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 8 (Java 1.8) support and broken pom since 1.3.37 #1033

Closed
Lonzak opened this issue Jan 23, 2024 · 3 comments
Closed

Java 8 (Java 1.8) support and broken pom since 1.3.37 #1033

Lonzak opened this issue Jan 23, 2024 · 3 comments
Assignees

Comments

@Lonzak
Copy link
Contributor

Lonzak commented Jan 23, 2024

I just tried to update to the latest version of openPDF (currently 1.3.39) however got an error related to the Java version.
I would like to ask for the reason to increase the minimum Java version?
This is quite a big change for a bugfix version. I didn't expect this from 1.3.36 -> 1.3.37. According to semantic versioning this is a breaking change and should have been version 2.0.0. Was there some newer feature the project wanted to use?

A lot of our customers are still based on Java8 so this means we'll have to continue to maintain our own iText fork. (I already started the migration to openPDF which means full stop now :-(

Additionally I would like to ask whether some other users have a java 8 requirement?

Side note:
The pom.xml seems broken since 1.3.37:
[WARNING] The POM for com.github.librepdf:openpdf:jar:1.3.37 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details

@andreasrosdal
Copy link
Contributor

andreasrosdal commented Jan 23, 2024

OpenPDF 1.3.37 requires Java 11 or later. This will allow modernization of the code-base using new features and syntax available in Java 11. Many other common Java libraries have begun to require Java 11 or later.

If you need to use Java 8 then you can use version 1.3.36 or earlier. If there is a need for more releases of OpenPDF supporting Java 8 then it can considered.

I recommend to begin encouraging your customers to upgrade to Java 11.

The latest version of the Spring library now requires Java 17: https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-Versions

Pdfbox also requires Java 11 now:
https://github.com/apache/pdfbox/blob/trunk/pom.xml#L130

@LibrePDF LibrePDF locked as resolved and limited conversation to collaborators Jan 23, 2024
@asturio
Copy link
Member

asturio commented Feb 20, 2024

I'm for updating the version of OpenPDF to 2.0.0 because of that. We could create a new "java8" branch from an appropriate commit (1.3.36?), but this branch would only get bugfixes, but no new features. Keep development for Java 11 for now.

I would link to this page of Eclipse Temurin: https://adoptium.net/de/support/
by now Java 11 and Java 17 will be supported until Oct 2027. So probably we need to make progress updating the java support.

I don't think keeping things in java 8 is a smart choice, even if this version is support until 2026. Everybody needs to move forward, and the only reason to stick with an old version of java, is if the software is also end-of-life.

I suggest paying attention to the version-numbers:

  • OpenPDF 1.3, should be compatible with Java 8
  • OpenPDF 2.0, should be Java 11 based
  • OpenPDF 2.1, should be Java 17 based
  • And Java 21 is the latest LTS Version

Not all libraries are now on Java 17, but as the environment (didn't find a better word) reach a certain level, OpenPDF should follow.

@asturio asturio reopened this Feb 20, 2024
@asturio asturio self-assigned this Feb 20, 2024
@asturio
Copy link
Member

asturio commented Feb 22, 2024

Closing this now, as there are now different branches for different releases:

@asturio asturio closed this as completed Feb 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants