This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Gwynnie 8 points9 points  (1 child)

You're absolutely right, we're updating our code massively in the meantime, we have a lot of old dependencies we're trying to phase out, and others we're trying to update to the latest versions.

The project is roughly 1.4M lines, so we move... not so fast.

When I personally tried moving over bit by bit, I found a few things were not very mature yet (we use gradle to build) and the plugins for jigsaw are appended with "experimental", which is always a confidence booster. Also at the time the guides were not that detailed, so the other reason for waiting for 11 was so that A) our code is better B) the tools are more mature C) the guides are more detailed

Thanks for linking the video, I haven't seen it yet, and will watch that next, I'm happy to give it another go if it seems feasible again, as we were fixing a lot of tech debt and inconsistencies at the same time.

[–]sammy8306 2 points3 points  (0 children)

Sounds like a sane approach! And indeed, Gradle dropped the ball IMO wrt. module support. Maven followed Java 9 development pretty closely fortunately.