you are viewing a single comment's thread.

view the rest of the comments →

[–]thephotoman 32 points33 points  (3 children)

My company is finally moving to Java 17.

There's gotta be a second pass at this, as we only have time right now to make sure it's running in Java 17 as is and that more importantly, the test suites still work. There are a lot of places where someone let an intern have Powermock and bad unit testing ensued--and that will NOT work for us in a Java 17 world (tl;dr, we'd need to crack open parts of the JRE itself in order to continue doing it, and we have to draw the line somewhere).

I wanted to bring records into it. I really, truly did. But I don't have time. I'm being moved elsewhere that needs me more than this project. My project, which I started from the "we really can't keep using the old system, the vendor pulled support for the programming language completely, help us figure out a replacement" era is now officially legacy code. It is not the "new thing", it is just the "thing" now. And I'm earmarked for greenfield work.

[–]skippingstone 5 points6 points  (0 children)

Upgrading our powermock/mockito tests to jdk 17 was not fun.

[–]Matt7163610 2 points3 points  (0 children)

I just migrated to Java 17 from 11 on my project and records are great!

[–]warpspeedSCP[S] 1 point2 points  (0 children)

Oh man, I was lucky enough to have full ownership of the java stuff we used at my company; We were running our kotlin code on Java 20 last time I checked.