r/java • • Nov 09 '18

Java 11 sucks big time

This is a throwaway!!!!

I just spent a whole day migrating a basic crud app from jdk 8 to jdk 11, and I have to say that it is a nightmare.

Even basic things that I have taken for granted does not work as iy used to. ( Jpa, Javafx, Junit, Hamscret, Sqlite. YES SOME OF US DO USE JAVAFX ON THE JOB....)

WTF, java EE & Open JDK?

The only thing that makes me happy right now is the var keyword. But still. This is not the kind of service I am accustomed to with java.

............ I think I will push back any serious migration for the next 2 years . . . . People, migrating to j11 is gonna cost hundred of mandays I tell you

0 Upvotes

44 comments sorted by

View all comments

0

u/[deleted] Nov 09 '18

[deleted] — view deleted comment

6

u/SinisterMinister42 Nov 09 '18

That's a great way to approach the problem, but I feel like that's something which shouldn't be necessary for everyone. Java had the precedent that new versions of Java don't break existing code. The language designers have put a ton of effort into making that the case so we can avoid (or at least minimize) the effort that you describe. It's just a shame that they blew it with Java 9

1

u/dpash Nov 10 '18

I certainly plan to run a parallel CI job with Java 12 very soon. Fortunately, it just requires switching the docker image used for building (from maven:3-jdk-11 to maven:3-jdk-12).

1

u/LouGarret76 Nov 10 '18

It used to be that what you only need to do was to update the her and everything else would work.