3 ms·
Not to brag but I recently ported our legacy java code base written for Java 1.5 to Java 8. The only change we made was to swap the jdbc jar as we also upgraded
by manishsharan 6y ago
Not to brag but I recently ported our legacy java code base written for Java 1.5 to Java 8. The only change we made was to swap the jdbc jar as we also upgraded our Oracle DB.
- oblio 6y ago8 to 11 can be a bit trickier, though. Subsequent upgrades should be boring again, but 8->9 can get interesting.
- thomascgalvin 6y agoI just upgraded a spring boot app from 8 to 15, and it was seamless. It's been long enough now that most major dependencies just work with 9+ again.
- EdwardDiego 6y agoTrying to upgrade stuff like Spring from 4.3 because you need 5.1 to run on Java 11+ is where we've felt the pain the most, but then we were doing some awful Spring stuff.
- spicybright 6y agoDamn dude, nice work. We've going 8 -> 11 right now and it's a pain in the butt.
- MockObject 6y agoWhat pain are you having specifically?
- erik_seaberg 6y agoA former co-worker wrote a saga about trying to use modules in today’s Java ecosystem: https://www.theoryofgeek.com/articles/fomo-java-module-edition https://www.theoryofgeek.com/articles/fomo-java-module-editi... TL;DR: anyone doing it wrong anywhere breaks you, and it’s only a win if you feel a need to rip pieces out of your JVM.