Well it was written that the artifact names were not JPMS compatible, you can review https://github.com/apache/geronimo-specs but it was just one example. Don't get me wrong but indeed you can fix all the world to make it fully JPMS compatible, this is not what happent since java 9 so I don't consider that path as something relevant today.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le jeu. 4 janv. 2024 à 14:31, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Le 2024-01-04 à 14 h 24, Romain Manni-Bucau a écrit : > > > > Cause it just works (and was forking for years). Geronimo specs jar > > have this issue for ex and this is not a blocker for lib builders to > > consume them, build with them and produce a JPMS friendly jar. > > > Still no test case for proving that it works? Link to the relevant part > of Geronimo build so we can check what they are doing exactly? > > Martin > >
