r/java • • Sep 01 '21

Spring 6.0 will be using Java 17 as its baseline

321 Upvotes

92 comments sorted by

3

u/21JGen Sep 02 '21

I wish android would do same too but I highly doubt it especially with the kotlin first approach

1

u/kartik1712 Sep 02 '21

Android is not Java. It does not even run the JVM so not sure what you mean here.

2

u/21JGen Sep 02 '21 edited Sep 02 '21

I meant is the required (Edit: or the baseline) jdk is 17 but it seems they will be stuck in java 7 and some parts of java 8 for a long time

4

u/kartik1712 Sep 02 '21

Yes, because they are not Java. They have most of the Java 7 APIs and some of the Java 8 APIs have been added using desugaring. Recently, they added some more new Java language level constructs using the same technique. The issue still remains that Android doesn't run on the JVM, it runs on ART. Hence, pretty much anything new in Java that utilises new JVM features can't run on Android. Plus, some Java APIs need to internally call into the JVM, you'd have to rewrite those or adapt ART to support it.

205

u/cogman10 Sep 01 '21

This is exactly the sort of kick in the pants the industry needs. It'll be hard to justify staying on 8 or 11 when the latest spring requires a minimum of 17.

71

u/TyPh00nCdrCool Sep 01 '21

Or they will stay on 5 forever and happily pay VMware for LTS.

20

u/TheCountRushmore Sep 01 '21

VMware?

6

u/ryosen Sep 01 '21

I'm guessing since Spring is developed by Pivotal and Pivotal is a subsidiary of VMWare, they are suggesting that Spring will charge for LTS on version 5.

3

u/nzipsi Sep 01 '21

More that Spring was acquired by VMware, then spun out as part of Pivotal, and then when Pivotal was acquired by VMware at the end of 2019, a lot of Spring committers essentially “came home”.

Strictly speaking, Pivotal was never a VMware subsidiary - it was a separate company controlled by Dell, so VMware was a sibling.

0

u/[deleted] Sep 01 '21

[deleted]

14

u/nzipsi Sep 01 '21

Well, Pivotal was spun out of VMware originally, who had acquired Spring some time before, so the 2019 acquisition was, for many Spring committers, more of a “coming home”!

4

u/Namenloses_Ende Sep 02 '21

And VMware belongs to EMC Documentum ... it's big enterprise companies all the way _down_.

(Blessed are those who have not had to develop 3rd-party integrations with Documentum...)

edit: correction, nowdays VMware seems to belong to Dell.

1

u/persicsb Sep 06 '21

VMware is publicly traded, you cannot tie it down to EMC or Dell. Of course, Dell is the overwhelmingly largest shareholder with 90+% of voting rights, but technically, VMware is not owned by Dell.

1

u/_PM_ME_PANGOLINS_ Oct 06 '21

Dell bought EMC.

-2

u/stefanos-ak Sep 01 '21

erm... Spring has actually changed many hands. There is no 1 company behind it, if you follow the history all the way back :)

0

u/[deleted] Sep 02 '21

[deleted]

4

u/pronuntiator Sep 02 '21

Spring 5, not Java 5.

6

u/DrFriendless Sep 02 '21

I'm on Spring 3.2.18 and Java 7. This just means it will be harder and harder to upgrade. I've been making the case for Java 8 for 3 years. I don't need a kick in the pants, I need products to make fewer breaking changes between versions.

27

u/westwoo Sep 02 '21

Maybe what you really need is a new job? Why tie your skillset to decrepit technologies that won't ever get updated?

7

u/DrFriendless Sep 02 '21

Because this is job is really really interesting. I use the latest version of Angular, cool AWS stuff, and get to invent new stuff. I just don't have the time to get a Java 8 version running and rebuild the server while people are using it 16 hours a day for work that pays my salary.

And I'll have you know that those technologies are no more decrepit than I am myself... I might just tell my boss that he has to let me upgrade to Java 8 before I die, because no newbie will have the cojones to even try.

17

u/westwoo Sep 02 '21 edited Sep 02 '21

Maybe I'm assuming too much, but to me it sounds like you're simply attached to this project :) we've all been there

My point simply was, it's not your last job, and the longer you stay the more stale your skills become. Your boss is potentially reducing your future salary and your opportunities on future projects in other companies for the sake of their own peace of mind and profits, which is understandable from their point of view, it's not like you matter - their project matters, these aren't your customers - these are your bosses customers. But you don't need to beg anyone for years to pick a more modern project that better aligns with your needs, and can let the boss deal with upgrades on their project in whatever way they want on their own according to their needs.

3

u/arijitlive Sep 02 '21

I agree, this almost has happened to me 3 years back. I was stuck using older spring based service oriented applications (both development and maintenance). Everything was stagnated in my life.

I learned spring boot and almost quarreled with my supervisor and changed to a different project. Now I am using SB2+Java11 along with multiple AWS techs.

2

u/phoneuseracc008 Sep 02 '21

Agreed this has happened to me rn

4

u/mauganra_it Sep 02 '21

Spring 3 on Java 7 is really old and requires a careful approach to get the upgrade right. It has to be done in multiple steps (newest Spring 3 patch, Java 8, refactoring to disentangle your code from the framework as far as reasonable, Spring 4 or 5, then Java 11) because doing it all in one would be insane. But first of all, you'd need a test suite that you can use to be confident that all important features still run.

3

u/jonatan-ivanov Sep 03 '21

Java 8 was released in 2014. I'm sorry that you are in this situation but do you think you will ever get the time to upgrade something you haven't for 7 years?

2

u/DrFriendless Sep 03 '21

I've only been in the job for 4 years. The previous developers did not seem to be very bold with respect to upgrades so I've had a lot to do. When I started we were on Java 6 and some ancient version of Scala, so I'm making progress. And I am increasingly cynical about using small third-party packages without a guaranteed future.

One problem with Java 7 is that one of the payment gateways we deal with requires ciphers that are newer than Java 7 and have never been implemented in the Java 7 VMs (AFAICT). When the payment gateway brought in that restriction we just couldn't use them, until I was able to get that part of the system running in Java 8. I've explained to the boss that we're looking at a doomsday scenario if whatever black magic that keeps the rest of the system's crypto working fails, but it still doesn't get prioritised.

1

u/persicsb Sep 06 '21

I'm sorry for you.

1

u/nomercy400 Sep 10 '21

You still don't use Java 8? I feel bad for you. No lambda's or functional-style programming. That is harsh. Also, the newer Spring versions assist with reactive programming, which I think would tie in really nicely with your Angular frontend.

I have had an upgrade project from Spring 2.x to Spring 4.3 a few years ago. It was the main product of a company, they wanted an upgrade. No test suite. As a single developer, took me 3 months of work. Reason we couldn't upgrade further was the heavy integration with Hibernate, which required bigger rewrites.

My plan of action: Clean & Upgrade

  • Figure out what maven dependencies are used. Go through each one of them, evaluate how heavily they are used, remove what isn't used. This can be done separately from the whole 'java 8 upgrade project', can be done during normal production hours, is much smaller to perform and will reduce your 'impact' surface when you do other upgrades. It will also likely make your application better to maintain.

  • You will now have a list of Spring dependencies.

  • Find all the Spring changelogs. Read through them, create a section per version and copy each line you think it might affect your application to a separate text file, i.e. if it affects Spring Integration and you use Spring Integration, then you copy the line. If it affects Spring Actuator and you do not use Spring Actuator, you can skip it. Again, this can be done without disturbing production or changing code.

  • You now have a changelog list related to Spring for your application.

  • Now starts the actual upgrading. Read through each version in your changelog file, determine if it might affect your code (this is the hard part), and update to that version. Then test.

  • Repeat until you hit a wall.

By cutting your upgrade path into smaller steps, you make the 'upgrading' more manageable. The major Spring upgrades are more of a hassle, but doable. You will likely have to make a bunch of configuration changes, as Spring likes to change defaults and introduce new configuration options. Also, Spring package names will change. These are the easy changes. More difficult are the upgrades to the subdependencies such as Hibernate, which can require major changes in your code, especially when deprecated parts are removed. This might be the 'wall' I mentioned.

Once you upgrade Spring, check your other dependencies. I tend to not use many other dependencies in a Spring project, either because they are already included by Spring, or because the functionality is so small I write it myself.

Usually when you have upgraded Spring, then upgrading Java can be done by simply changing a 1.7 in an 8, or an 8 into an 11 (+ some package name changes or javax maven dependencies), or an 11 into a 16.

Using the 'Latest Angular' and 'Cool AWS stuff', but sticking to an ancient version of Java sounds to me like you don't like working on backend or be full-stack, but rather want to build front-end and cloud things. Reflect on yourself, is this also how you feel? If so, you might want to focus your career in that direction and let somebody else manage the backend.

1

u/DrFriendless Sep 11 '21

Oh yeah, I've done this stuff before. I even used Java 8 before I started this job. Some of the code base is Scala, and the front-end is TypeScript, so the FP stuff is not new to me. In fact my Ph.D. is in functional programming... but having said that, I don't like at all the lazy collections in Java 8.

So I've done as you said, and I got the bad dependencies down to 2. We use ElasticSearch 1.2.1 - no that is not a typo - when the earliest documented version of ElasticSearch is 5.something. So I refactored that to be behind an interface, and implemented that interface in 1.2.1 and some more recent version which works with Java 8.

That left only GWT - Google Web Toolkit. There's maybe 20000 lines of GWT so that must be preserved. The last time I tried to get running in 8, there was one method that had changed incompatibly, which was called in maybe 150 places. So I changed them, but then although nothing was obviously wrong, the GWT would not compile and just gave the most useless error message. "Computer says no", sort of quality.

The GWT was spread across two modules, and one of those was because of an obsolete architectural decision, so I refactored that module out of existence. Since then though I have not got back to the Java 8 project.

But the code is not the only complication. Because we use Java 7 and ElasticSearch 1.2.1, we need to deploy on Ubuntu 14... and to deploy on Java 8 I will need a bunch of different versions. Rebuilding that server takes maybe a day, so that's a site down issue which is why I can't hide this project from the boss :-).

One thing that pisses me off in this is that ElasticSearch does the Stupid Beyond Fucking Belief thing of screwing with the bootclasspath at runtime. There is no in Java 8+, I believe, so that cant ever work. I'm sure it seemed like a good idea at the time, but it was not.

Yeah, so that's how someone gets into this situation. If we could turn the business off for 2 weeks I could easily solve the problem, but that's not an option.

In response to your closing comments, you're totally wrong :-). I was previously a back-end Java dev on a project, which started on JDK 1.1 and was on 1.7 when I finished. We were on 1.1 because that was the latest... but when I started this job, it had an existing back-end and the Angular project was new. That was when I became a full-stack dev. I am the ONLY dev, and we can't afford another - the company is too tiny. So I do the Java, Scala, TypeScript, AWS, MySQL, user experience, tech support, and respond to the technical parts of tenders.

My feeling is that this is my job, I gotta do what I gotta do. If I could dump one bit it would be the Scala, which has not grown on me. I could theoretically look for another job, but who would replace me?

0

u/[deleted] Sep 02 '21

[deleted]

1

u/TheCountRushmore Sep 02 '21 edited Sep 03 '21

Agreed. Those who are still on Java 7 at this point aren't Java users they are Java 7 users.

No reason for the Java 7 users to concern themselves with the forward progress of the ecosystem and no reason for the ecosystem to concern themselves with the Java 7 users.

48

u/metalhead-001 Sep 01 '21

I welcome this. Things in the Java world have been far too conservative for a long while.

I really hope that the Spring devs will use this as an opportunity to clean up much of the legacy junk in the codebase and make things faster/better.

65

u/pjmlp Sep 01 '21

Great news! Even if I rather use other frameworks, Spring really adds pressure to the ecosystem to move forward.

15

u/TheCountRushmore Sep 01 '21

Agreed. I don't use Spring, but this moves the needle even if it is just for greenfield projects for a while.

16

u/JumboTrout Sep 01 '21

Other frameworks? Besides Jakarta, what others are there? Serious question btw.

26

u/IntelHDGraphics Sep 01 '21 edited Sep 01 '21

Quarkus, Micronaut, Play! (today it's mainly used with Scala instead of Java, but you can still use Java) and others not so popular in 2021 like Struts

10

u/cryptos6 Sep 01 '21

My impression is that there is not much power behind Play these days. It was a different story 5 to 10 years ago. In common developer surveys this framework is only a side note.

0

u/[deleted] Sep 01 '21

[deleted]

0

u/thomascgalvin Sep 02 '21

I used Dropwizard a few years back and really liked it, but Spring offers so much more out of the box.

2

u/benevanstech Sep 02 '21

It's very difficult to get accurate numbers about this aspect of the ecosystem. Beyond "lots of people use Spring", which we pretty much knew, there isn't a good way to be scientific about this - especially given the reliance on self-reported surveys.

Dropwizard is surprisingly popular. Quarkus and Micronaut are probably both also under-reported, but for Quarkus it's really Native that a lot of people are thinking about.

Also - the fact that so many people are very slow to upgrade Spring means that it's not really as much of a monolithic ecosystem as it appears - we should probably subdivide Spring by major versions.

5

u/Computer991 Sep 01 '21

Most companies I've talked to today aren't using Spring; Quarkus, Micronaut are the two biggest ones I hear about, or KTOR if you're running Kotlin

20

u/TonyNickels Sep 02 '21

Spring is still an industry leader.

1

u/[deleted] Sep 06 '21

Quarkus is mostly used for AOT deployments where low memory consumption and fast startups are necessary. Spring Native is the answer to Quarkus which is quite nice but still work in progress. Basically the choice is not between Spring and Quarkus, the choice is between JIT and AOT. Each one comes with its own advantages and disadvantages. I haven't heard about Micronaut and Ktor.

Most companies I've talked to today aren't using Spring

I'm sorry to hear that. Backend and middlewares are a solved problem for 99% of the applications. I would never risk it with anything else. Though, Quarkus is alright, but once Spring Native stabilizes, I will focus on that since my team can reuse the knowledge.

1

u/Computer991 Sep 06 '21

I'm sorry to hear that.

Nothing to be sorry about tech stacks move forward Spring Boot isn't the best solution for Kotlin and there is always room for improvements even in spaces where problems are "99% solved" :)

1

u/[deleted] Sep 06 '21

Yes, guest languages on the JVM have a reputation of being hyped in the beginning and then abandoned as the years pass. I've burned myself twice, one time with Play Framework in Scala and the second time with Django in Python. Both frameworks managed to create a mess of everything and man, the backwards compatibility was catastrophic. The first one was the Python 2 to 3 craze and the second time was typical Scala clusterfuck. Kotlin though found a niche in Android.

64

u/Barbossa3000 Sep 01 '21

way to go. good bye java 8

51

u/OneOldNerd Sep 01 '21

You underestimate the inertia of some companies.

15

u/andrewharlan2 Sep 01 '21

Still on Java 8. RIP me. :(

18

u/Kagron Sep 01 '21

Still on Java 5. :( I wish I could use Java 8 or 11

15

u/Cpowel2 Sep 02 '21

Damn I thought being in 8 was bad. I feel for you working in 5.

10

u/haakon Sep 01 '21

Java 5 came out in 2004. How can you still be stuck with it? Is there even commercial support available?

16

u/Kagron Sep 01 '21

Unfortunately, our clients are state governments and other various public entities. So imagine the slowest company and multiply it by 10. So many reasons why they can't update: budget concerns, laws, "if it works, it works" mentality, etc etc. A lot of them are on 8 but we still have some on 5 and we gotta program to our lowest common denominator :(

5

u/Muoniurn Sep 02 '21

Wtf.. do they also run windows xp? How is such old software not a security risk?

1

u/spiglebach Sep 02 '21

Exactly... We had a webapp that government ppl used and they did not understand why it behaves weird on their Internet Explorer browser

2

u/blobjim Sep 01 '21

The only thing I could think of is Blu-Ray or something which probably uses an even older version of Java.

5

u/nutrecht Sep 02 '21

I wish I could use Java 8 or 11

You can. At a different company :)

6

u/s888marks Sep 02 '21

Java 5? That's modern. I had to look up something in the JDK 1.1 javadoc today!!

7

u/metaquine Sep 02 '21

luxury! I had to build Java with a Makefile once!

3

u/jdavidw13 Sep 02 '21

Guess I can't brag, our recent upgrade was to 7.

4

u/OneOldNerd Sep 01 '21

Same
/wrists

4

u/13steinj Sep 01 '21

Forget inertia, many just don't care.

There's companies that have a variety of tooling all built in Java 8. And they continue to build brand new tools, in Java 8. Many of which do not use Sun internals.

7

u/[deleted] Sep 01 '21

When the upgrade from 8 to 11 breaks a "bunch of shit" I don't think it's inerta that's keeping peopel on 8. My company moved from 4, 6, 7, 8 relatively quickly. We're working on 11 now (with the expectation that once we have it all working on 11 we'll jump to 17 near instantly). But the whole backwards compatibility strength of java got hit HARD from 8 to 9. I get why they did it, but it's a very real thing that is dangerous for companies to handle without devoting a lot of time and effort into doing right. Aside other "business things", it can backburner for a long time.

11

u/pron98 Sep 02 '21 edited Sep 02 '21

But the whole backwards compatibility strength of java got hit HARD from 8 to 9.

This isn't quite what happened, though. Java 9 is nearly 100% backward compatible with 8 (there were, I think, around four methods that no one had used that were removed); even 11, once you add the separated EE modules, is virtually 100% compatible with 8. Almost all issues people had upgrading at first were due to libraries that, for various valid reasons, were written for Java 8 with the intent to not be portable to future versions (i.e. they depended on internal implementation details). So parts of the ecosystem ossified around 8, and even though Java (the public APIs) remained virtually unchanged, the changes to the implementation broke many of those non-portable libraries. That's why, as of JDK 17 (or, by default, as of 16), Java enforces strong encapsulation that hides JDK internals from libraries unless the application approves their use. This way you, as an application developer, would at least know that you have libraries that are a maintenance risk, and the problems we had going from 8 to 9 won't return.

-5

u/[deleted] Sep 02 '21

This isn't quite what happened

Oh please, do go on.... :popcorn:

4

u/benevanstech Sep 02 '21

Serious question: When was the last time you tried to move to 11?

Java 11 came out in Sept 2018. For the first few months, it was somewhat problematic, but by June 2019 most of the migrations I saw were trouble-free and by Jan 2020 it was plain sailing - just upgrade Java, upgrade dependencies (& add in standalone JAXB if needed).

Oh, and retest to check the containers were right-sized & make sure to count all the actual monetary savings that the company was getting by upgrading and tell your boss about them, of course.

1

u/[deleted] Sep 02 '21

Sorry, I must have missed something - what exactly changed over that time to make migrations "easier" ? I already know exactly what needs to happen to make the migration happen, it's a lot of underlying dependency changes that, unfortunately, are generally hidden by the fact that we've imported interface packages to compile against that now require other interface packages to compile against along with their implementations.

I'm not even touching on the very real "there's some internals that your libraries might be using that are not good to use anymore" issue. I mean, that's very much a likely non-issue, but it's one of those "okay, so something might be broken in your codebase, but you won't know until you do it, HAVE FUN!" We keep our dependencies pretty up to date so I'm really unconcerned here, but it's still one of those things that's going to come out with the users as bugs which -- I'm going to be kind here -- is actually important and critical for us.

5

u/benevanstech Sep 02 '21

The major issue in 2018-early 2019 was transitive dependencies on libraries like ASM.

If I depend upon libs A & B at versions X & Y respectively, and they depend on ASM version Z (which does not support Java 11), I can't upgrade fully safely until A & B have released new versions that depend upon a version of ASM that does support 11.

AFAIK, by late 2019 there were only a few common dependencies that weren't 11-compatible, and only a few remaining edge cases by late 2020.

The internals issue is, in my experience (shepherded dozens of apps through the upgrade), pretty much a non-issue, as you note. And, yes, in the very unlikely case they do affect you, you will catch them in prod.

But what's the alternative? If you're struggling to find the time to do an upgrade that basically involves wading through a full dependency bump and a spring clean of your build files, then you probably don't have time to go through your dependencies with a toothcomb to look for rogue uses of internals, even if you're 100% sure that you know what to look for.

1

u/[deleted] Sep 02 '21

As I've noted elsewhere, it's going to happen. I just wanted to point out in the original reply that for some companies it might be inertia, I don't feel that's the primary reason why companies are not moving from 8 to 9/11+. I'm sure it's that for some, but they're probably still on Java 7.

5

u/benevanstech Sep 02 '21

Well, our opinions differ. I don't believe there are that many companies for whom the 8 -> 11 migration story is very difficult these days. Of course, there are edge cases (e.g. component from supplier who went out of business that accesses internals inappropriately) but in the main - it's a simple matter of bumping dependency versions, adding anything required by the new versions and you're done.

I think it's far more significant that there are lots of containerized applications out there that are literally throwing money away by *not* upgrading to 11.

5

u/[deleted] Sep 02 '21

Containers is probably the "why" for why we are upgrading to 11. The other one is Project Loom. While it's not in 11/17, we'll need to get there before using it. Why anyone would do Java8 containers is beyond me. As you note, throwing away money.

1

u/OneOldNerd Sep 02 '21

Agreed. However, even the mere mention of "breaking changes" makes management break out in a rash, so much so that they don't even want to discuss what would be involved moving away from 8, when they probably should.

1

u/[deleted] Sep 02 '21

Yea, we're moving to 11 soon™. Everyone knows (most of) the issues, it's just a matter of doing it at this point. It's just not inertia that's holding it back, it's a fair bit of work combined with risk.

6

u/mark1x12110 Sep 01 '21

A little aggressive in my opinion. Many libraries are still working to implement Java 11

I agree with the idea of killing Java 8 though

26

u/kartik1712 Sep 01 '21 edited Sep 01 '21

I think Java 11 -> Java 17 will not be as tough as Java 8 -> Java 11. The main issues in migrating from Java 8 -> Java 11 have been stronger encapsulation of JDK internals and the module system. Adding Java 11 support in a library is often synonymous with some support around these two things.

That said, Java 17 changes the illegal access warnings to errors. However, most libraries that have added Java 11 support eliminated the illegal accesses. So it is a non-issue for those libraries and their consumers. Those libraries which still have illegal accesses would have received bug reports already since the default was changed in Java 16. Java 17 will be out later this month and Spring 6 is slated for Q4 '22. That gives the library maintainers another year to get "ready" for Java 17.

5

u/krzyk Sep 01 '21

Well, in 17 the encapsulated it completely. There will be similar problem like with Java 9 (which was one that did that AFAIR).

7

u/kartik1712 Sep 01 '21

Its not encapsulated completely. They removed the global escape hatch --illegal-access. The --illegal-access flag was only there to serve as a transition. If a library or the application needs access to the internals, the user can provide --add-opens. That's the intended and supported way to access JDK internals.

1

u/krzyk Sep 01 '21

Well yes, but this is a big change, just like the previous one.

13

u/nicolaiparlog Sep 02 '21

It's the same change again if that makes any sense. You only need to stop using internals once - either when going 8~>11 or when going 11~>17.

15

u/reqdk Sep 01 '21

I think Java 11 -> Java 17 will not be as tough as Java 8 -> Java 11.

There's a psychological barrier there for some folks who see big numbers and get freaked out, even though chronologically, Java 11's release is way further from Java 8's than Java 17's is from Java 11's.

13

u/lonelyWalkAlone Sep 01 '21

what does spring 6 offer as new features? is there some speculations on this?

4

u/gavenkoa Sep 01 '21

I remember Spring series 3.x. They moved fast and wrapped a lot of things into beans. Spring Test Framework was huge for me. Later I updated Spring because of Boot Framework and Boot 1.x => 2.x was a bit transition.

Nowadays I don't understand why I need to update Spring platform: for mystical "security" fixes? It just works ))

8

u/hwaite Sep 01 '21

Awesome. Trying to make Jigsaw work with Spring has been a nightmare on 5.x.

2

u/cryptos6 Sep 01 '21

What was so hard about it? Wouldn't you just need to open the modules for spring?

1

u/hwaite Sep 02 '21

Old Spring doesn't use explicit modules. Internal packages are exposed willy nilly. Also, there are 'split package' issues. Lastly, Spring imports a bunch of non-modularized dependencies. Maybe the release of 6.0 will incentivize others to finally get with the program.

8

u/nimtiazm Sep 02 '21

That’s a great move. Frameworks and libraries with large adoption rate often move the ecosystem. Spring is undoubtedly a giant in the Java ecosystem.

3

u/olivergierke Sep 02 '21

Jürgen has just published a couple of details about that move on the Spring blog: https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6

1

u/xCuriousReaderX Sep 02 '21

Should have waited for project loom instead

-14

u/sweetno Sep 01 '21

Wow-wow-wow! But I doubt they'll actually use new features of Java 17 (or 11).

10

u/[deleted] Sep 01 '21

Why wouldn't they? What would be the point of requiring JDK17 if it wasn't to take advantage of it?

0

u/[deleted] Sep 01 '21

[deleted]

7

u/Nalha_Saldana Sep 01 '21

Do you run 16 without the allow illegal access flag? That seems to be the huge step to 17 that holds a lot of dependencies back.

2

u/TyGirium Sep 01 '21

I do, but I have also ~ 15 add-opens flags added to my startup script

6

u/[deleted] Sep 01 '21

[removed] — view removed comment

1

u/lonelyWalkAlone Sep 01 '21

You're lucky you're using Java 8, some banking companies still have legacy code running under java 6 and 7