This is essentially how my upgrade from JDK8 went. When 9 was released I spent about an hour giving it a spin and hit many issues. I filed some bug reports and went back to developing on 8.
When 10 came out I did the same thing and got a little closer.
Being a Java EE project 11 caused many issues with the removals. 12 had one annoying bug with Apache POI, and finally everything was green on 13.
The point is I didn't lose a bunch of sleep over the migration. I gave it a couple hours every 6 months and did what I could to assist the projects that needed help getting things compatible.
If I was still on 8 at this point I would start trying to get things to work on JDK 17-ea. I think most tooling and and libraries at this point are working fine, and if they aren't and are stuck on JDK8 then it's probably time to evaluate if they are a good long term dependency for your project. They wouldn't be in mine.
8
u/TheCountRushmore Jun 15 '21
This is essentially how my upgrade from JDK8 went. When 9 was released I spent about an hour giving it a spin and hit many issues. I filed some bug reports and went back to developing on 8.
When 10 came out I did the same thing and got a little closer.
Being a Java EE project 11 caused many issues with the removals. 12 had one annoying bug with Apache POI, and finally everything was green on 13.
The point is I didn't lose a bunch of sleep over the migration. I gave it a couple hours every 6 months and did what I could to assist the projects that needed help getting things compatible.
If I was still on 8 at this point I would start trying to get things to work on JDK 17-ea. I think most tooling and and libraries at this point are working fine, and if they aren't and are stuck on JDK8 then it's probably time to evaluate if they are a good long term dependency for your project. They wouldn't be in mine.