gnodet commented on PR #12135:
URL: https://github.com/apache/maven/pull/12135#issuecomment-6012611294
The `Automatic-Module-Name` in compat modules is deliberate: it reserves a
stable module name in case downstream consumers reference these JARs from a
modular context (e.g., `requires org.apache.maven.artifact`). Without it, the
derived name from the JAR filename is fragile and can break between releases.
These modules stay on the classpath — no `module-info.java` is added, so
there's no split-package conflict at runtime. The `Automatic-Module-Name`
manifest entry is a no-op for classpath usage and only matters if someone puts
the JAR on the module path, where it gives a predictable name rather than a
filename-derived one.
That said, if the concern is that it's misleading ("looks modular but split
packages prevent real module-path use"), I could see the argument for removing
it. But Maven 3.9.x already ships `Automatic-Module-Name` in many of these same
JARs — dropping it in 4.x would be a regression for anyone who already
`requires` them.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
