On 7/26/2023 1:42 PM, Martin Desruisseaux wrote:
… If a dependency is on the classpath, then the dependency is loaded as an unnamed module, its "module-info" file is ignored and the services that it contains are not discovered.
Can you elaborate on the last point a little more? I haven't modularized my core libraries yet, and want to know how they would work with non-modularized applications.
You say that if the modularized library is put on the classpath, its services are not discovered. But wouldn't normal pre-module-era classpath-based service discovery still work via the `META-INF/services` configurations in the library JAR files? Please clarify what won't work if I modularize my core libraries, which contain services to be discovered, and I try to use that with a non-modularized application.
Thanks, Garret --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
