Rely on the ML-Specification version present in the ModLauncher environment rather than on the Package specification version, since that version is unavailable in two scenarios: 1) ML loaded as a JPMS module and 2) ML added to the classpath using a folder rather than JAR-file.
Fixes #656
p.s.: I do not know how to test this using ModLauncher 4, to be honest. And it obviously needs more testing in general.
Rely on the ML-Specification version present in the ModLauncher environment rather than on the Package specification version, since that version is unavailable in two scenarios: 1) ML loaded as a JPMS module and 2) ML added to the classpath using a folder rather than JAR-file.
Fixes #656
p.s.: I do not know how to test this using ModLauncher 4, to be honest. And it obviously needs more testing in general.