On Wed, Nov 3, 2021 at 12:54 PM Benjamin Evans beevans@redhat.com wrote:
Hi,
On Wed, Nov 3, 2021 at 10:32 AM Mikolaj Izdebski mizdebsk@redhat.com wrote:
I've ported all my packages to be buildable with OpenJDK 17. I have not pushed the changes to dist-git yet, but I will do it before the end of the week.
I wanted to share common problems I encountered and solutions I came up with. I hope that this will help others trying to port their packages.
Problem 1: Compiler source/target levels 1.6 are no longer supported Solution: Bump source/target levels to 1.7 or 1.8
Just a general plea to please use 1.8 not 1.7 as a baseline - Java 7 was EOL'd 6 and a half years ago, and according to the most recent data I have that I regard as trustworthy, its usage is <0.1% and down in the statistical noise.
In my opinion, we really shouldn't be enabling the use of this outdated tech, which is very likely to be deployed in all sorts of very insecure ways.
IMHO our packages should be as close to upstream as possible. To the possible extent we should respect upstream decisions to target ancient, no longer supported Java versions. Therefore in cases upstream targets Java < 1.7 I made the packages compile with 1.7 compatibility, which is the lowest version still supported by OpenJDK 17.
-- Mikolaj Izdebski
Thanks,
Ben