Java Modules in Real Life

Many Java projects (by some counts, over half) run on Java versions that support the module system and Maven Central offers over 4.200 modules. If you think about creating modules for your (next) project, you may have some questions:

Why use modules?
- Incremental modularization
- What are common or tricky roadblocks?
- Where's the exit?!
- When (not) to use modules?

In this talk, I'll answer these questions, so you can better decide whether modules are right for your project.

Speaker's name: Nicolai Parlog
Speaker's title: Developer Advocate
Speaker's organisation: Oracle

Speaker's bio:

[NigelJones]

really useful presentation. I’ve recently looked at porting our open source libraries (400+ modules) to JPMS and it wasn’t too bad at all - so far. decided to watch this afterwards to check what I’d learnt, and think I’m on the right lines!

[steveeuphrates-river]

This was a kick ass presentation. Thank you!

[warnoggin]

Great presentation with lots of really useful information and explanations!❤

[black-snow]

Insightful but I expected (and need in order to really grasp) some hands-on. What do I actually have to care about when I use maven/gradle/ant ...
What about java8 runtimes? Do they still work with modularized stuff?

[allesio]

Lots of useful info, but missing code examples.

[KoenZyxYssel]

For a while I had some real issues with my javaFX dependencies but I think switching to Maven took care of all that. Not sure if we Apache commons stuff is modularized yet but I had to do some weird stuff to make jmod files in order to get those to work. Anyway, I'll have to read that stuff on dev.java to get a better grip on this stuff.

p.s. Around where you started talking about the uber jar I started hearing you speak like a belter from the Expanse, I wonder what that accent is... That show has almost as many problems as Lost.

[georgetsiklauri]

Talk is super fast, very superficial and of unclear structure. Also, modules are not to make "dependencies more explicit" (this is even further confusing wording..) or it's not to "solve why something compiles" problem.. For the next talk, I would suggest to have a slower and clearer approach, with a consecutive pattern, starting with A and going to B, without rocket-speed rush.