On Sun, May 25, 2025 at 7:14 PM Hunter C Payne <hunterpayne2...@yahoo.com.invalid> wrote: > > I believe JPMS has been around for something like 15 years. And after 15 > years of pushing it hard, it doesn't seem like it is used by too many people.
Java 9 introduced the Java Platform Module System (JPMS) in September 2017 — just eight years ago, not 15. Many "enterprises" remain on Java 8 due to legacy constraints, limited migration incentives, or risk aversion. Even within open source ecosystems, adoption of JPMS has been limited, despite its clear benefits for modularity and encapsulation. In that context, eight years is not a long time — but even so, there hasn’t been a significant or coordinated push to promote JPMS adoption. > If people are not using it by now, how good of an idea is it to push it now? > I feel like the market has spoken (over and over again) on this topic. My > experiences with JPMS have been universally been bad. If you are going to do > this, you need to make the default for it to be completely disabled. If you > don't, don't expect adoption of M4. As Martin mentions, this is your experience of JPMS, or your experience of Maven 3 / Gradle support of JPMS? In my experience, JPMS has helped me write better-structured code. Adopting a modular mindset is challenging at first, but once understood, it pays off. That said, I recognize that many developers prioritize speed and convenience over clean architecture — leading to issues like split packages and poorly designed APIs becoming the norm. What I found most difficult was the lack of tooling support. Tools like Maven 3 and Eclipse IDE had limited support for JPMS, which forced me to implement awkward workarounds — especially when working with multi-release JARs (MR-JARs), where support was almost nonexistent. If Maven 4 addresses these limitations, it would be a much-needed improvement for developers looking to adopt JPMS more seriously. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
