Set Automatic-Module-Name in standalone JAR #4079
Description
Running jar --describe-module --file junit-platform-console-standalone-X.Y.Z.jar yields:
No module descriptor found. Derived automatic module.
junit.platform.console.standalone@X.Y.Z automatic
requires java.base mandated
provides java.util.spi.ToolProvider with org.junit.platform.console.ConsoleLauncherToolProvider
provides org.junit.platform.engine.TestEngine with [...]JupiterTestEngine [...]SuiteTestEngine [...]VintageTestEngine
provides org.junit.platform.launcher.TestExecutionListener with [...]UniqueIdTrackingListener [...]OpenTestReportGeneratingListener
contains junit.extensions
contains junit.framework
contains junit.runner
contains junit.textui
contains org.apiguardian.api
contains org.hamcrest
contains org.hamcrest.core
contains org.hamcrest.internal
contains org.junit
contains org.junit.experimental
contains org.junit.experimental.categories
[...]
contains org.junit.vintage.engine.support
contains org.opentest4j
main-class org.junit.platform.console.ConsoleLauncher
The name of the derived automatic module is based on the file name - which is unstable if users or build tools rename the JAR file. It would be better to provide a stable name in the JAR's manifest for when the standalone JAR is put on the module path. As this JUnit Platform standalone JAR is often used as a drop-in replacment for JUnit 3/4, the automatic module name should be junit - just as the junit.jar has it since 2018 via: