Hello
If I'm understanding right, Maven put a dependency on the module-path
instead of the class-path only if:
1. the dependency is modularized (contains a "module-info" file), and
2. the project using the dependency is itself modularized.
Condition #1 is fine, but #2 is problematic. 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. Not only the services that the non-modularized project may
be looking for (I understand that it may not work), but the modularized
dependency itself cannot find anymore its own services, or the services
of its modularized dependencies, if those dependencies were not on the
module-path.
Is there a way to force Maven to ignore condition #2 and use only
condition #1 for deciding whether to put a dependency on the module path
or not?
Thanks,
Martin
