Inconsistency with service loading by layer or by class loader

[Ron Pressler]

> On 12 Dec 2024, at 14:35, David Lloyd <david.lloyd at redhat.com> wrote:
> 
> The problem is that 100% of these frameworks are required to work on the class path as well (and some are not yet being tested on the module path, or even defining an automatic module name, though I've been working to improve that for a couple years now).

If this is not because these frameworks still support JDK 8, could you explain why a single JAR should work both on the classpath and the module path, given that the two can be freely mixed? I've heard of such issues, but never in much detail, and my sense was that they stem from build tool limitations that would more easily and naturally be fixed by the build tool.

— Ron