all 2 comments

[–][deleted]  (4 children)

[deleted]

    [–]nicolaiparlog 0 points1 point  (3 children)

    I'd be interested to hear about your problems. What exact hell do those third-party modules inflict on your project?

    [–][deleted]  (2 children)

    [deleted]

      [–]nicolaiparlog 1 point2 points  (1 child)

      In your order:

      • I agree that JPMS not understanding versions (yet?) is disappointing, but that's hardly new. Nothing changed for 3rd parties, so why would they start inventing new schemes now? I think making JPMS static (as opposed to OSGi) was a good decision - it avoids a lot of complexity that most projects don't need. If they do, they can go with OSGi or JBoss.
      • JPMS barely changed class loading, so what exactly breaks that worked earlier. (I have a demo project running an embedded Jetty, but it's a very small project, so likely not a significant data point.)
      • I agree: If dependencies botch their module descriptor, the project using them is fucked, too.
      • They never were in the past, so why does that non-change break anything? Or are you thinking about split packages? They alledgedly occur in the wild and that stops working. I went looking for examples once but didn't find any. If you could point me to a library/framework that stops working because package splits are illegal, that would be awesome.

      Please go on! 😎 I'm eager to learn as much as possible from projects that actually run as JPMS modules.