-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
Increase JDK baseline to Java 8 (Woodstox 7.0.0) #134
Comments
Java 8 is a requirement for many other libraries nowadays. There definitely is precedent for upping the Java version in a minor update e.g. commons-io, commons-compress, and common-lang all did so. |
Thank you @dan2097. |
Very weak argument. This is the same argument as getting a new mobile phone every two years just because your operator provides you a new almost one because you extend your contract for another two years. An upgrade makes sense if you are going to use those features. Regarding Commons: I consider this a dick move from my fellow Commons committers because those libraries are use EVERYWHERE and they should have stayed at 7 until next major. |
Wow. Please tell us how you really feel @michael-o :-) I don't think comparison here is particularly apt: Java 8 has been around for a while and has really become the new baseline for anything not migrating to the new module world. But I'll keep this in mind as -1 against upgrade; I will probably reach out on mailing lists too before making decisions here. Finally, note that previous 6.x version would remain JDK 6 and branch technically speaking open. |
+1 on the major version bump for a baseline change. |
For clarification: I don't mind going Java 8 at all, but it has to be justified and the code should use Java 8 features. Just Java 8 class version won't make it Java 8. |
I'm not arguing that one should update for the sake of it, but the state of the Java ecosystem is important. If the other "base" dependencies are on Java 8, then any complex project must neccesarily also be on Java 8+. If the downsides are small, the upsides to justify an update only have to be relatively small. For a start as @cowtowncoder points out the lack of tooling support in GitHub Pipelines introduces overhead in guaranteeing that the project actually still builds on Java 6/7 There's also various quality of life improvements e.g.
|
Quick note: I think this upgrade (which I am in favor of) should bump Woodstox major version to 7. |
Quick note: here we are, 2 years later :-D I am trying to close out 2 feature PRs first, for 6.6 I hope; and after this can consider the bump. |
Currently Woodstox 6.2.x only requires Java 6 for compilation and running, but time is probably ripe to move to Java 8 baseline since that is the oldest actively supported JDK/JRE version.
On Woodstox version bump: this cannot be done in a patch release for sure, but although some might argue this requires major version increase, I feel it is more of a minor update in this particular case. Most users have migrated and due to slow trickle of fixes for Woodstox itself, systems running on pre-Java 8 have no urgent need for updates.
So I don't think there is much downside to making this change for Woodstox 6.3.0.
The text was updated successfully, but these errors were encountered: