Fork me on GitHub

Buenos dias


Good Morning!

djm07:03:36 - talking about Java 17, As is possible in Java 9 through Java 16, it will no longer be possible to bypass strong encapsulation via the command-line option, --illegal-access - it's a shame they didn't leave it there for the LTS


I'm not sure what is served by doing this? I'm getting more and more of the opinion that this sort of behaviour where LTS is not considered is a big ill in the industry...


From what I've heard, uptake of any version of Java after 8 (including 11) is relatively low, but more people are expected to want to move to 17, so it seems like a pointless extra barrier to put in the way of that


But maybe there's a good reason why they wanted to kill it sooner rather than later 🤷


I mean it seems like they implemented the best solution, just add it as a flag, why now go through the extra effort of removing it?


Keeping things around isn't free - they have to be made to keep working, may make other things harder, etc. I don't know how much that applies here


We still get a warning from the New Relic Java Agent about illegal access and they’ve had at least one ticket open for years with folks complaining about it still being there with each new JDK release — I guess at least they’ll have to fix it now in order to be JDK 17 compatible.


Updated the NR issue on GH about it with a note about 17 and a link to this article. Sigh.


@U015KH5ENEM That's fair, but in a sense it's also a really easy answer? Perhaps it's a necessary removal, but I do feel at times people opt to remove to save some effort at the cost of backwards compatibility.


I'm not qualified to answer about the specific case, but they generally do a very good job with backwards compatibility, and the warning will have been there for four years by the time Java 17 is released (and 11 will still be supported for a while after).