How changed JPMS between JDK17 and JDK18?

[dmatej]

I have to face one issue I discovered when working on #25183 - When I mix modulepath and classpath even with good separation of these two "segments", classpath specified in jar's manifest file doesn't work for JDK11-17, while it works perfectly with JDK18-23.

My question is what changed in JPMS between 17 and 18 that changed this behavior? Can somebody give me a link to OpenJDK JIRA? I tried to search here, but maybe I am too tired: https://bugs.openjdk.org/browse/JDK-8218268?jql=text%20~%20"Manifest%20Class-Path"%20AND%20created%20>%3D%20-300w%20ORDER%20BY%20fixVersion%20ASC

The current solution is to specify classpath on commandline which is not exactly what I would like. Those "fake index jars" like jakartaee.jar, glassfish-embedded-static.jar were quite helpful to simplify the commandline - and they still do work on Java 18+. Another option is to always create custom classloader like GlassFishMain does. However I would expect something simple ... even for JDK11-17 ...?

[dmatej]

Well, immediately after I asked I have found this: https://bugs.openjdk.org/browse/JDK-8273473
At some point I added <index>true</index> as an experiment to maven-jar-plugin and forgot about it ... as I wrote this question it rang the bell ... seems locally the ejb_group_embedded passed with 17, hurray!