You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b94c80c
Browse filesBrowse the repository at this point in the historyBrowse files
build: declare Automatic-Module-Name for all published jars
Modular (JPMS) applications cannot depend on this project because none
of its published jars declare module information, so the JDK falls
back to deriving an automatic module name from the jar filename - a
mechanism the JDK itself documents as unstable across releases and
unsuitable to depend on in a `requires` clause.
This adds an explicit, stable Automatic-Module-Name to every module,
configured centrally in the parent's maven-jar-plugin management and
set per-module via a new automatic.module.name property. Names are
chosen to match each module's root Java package (e.g.
io.awspring.cloud.sqs for spring-cloud-aws-sqs) so they remain valid
if any module later migrates to a real module-info.java.
This is intentionally scoped to the automatic-module-name step only,
not full JPMS modularization (module-info.java per module), which
would need further design input on package/export boundaries.
Verified by building affected modules and inspecting the resulting
jars with `jar --describe-module`, confirming each now resolves as a
named automatic module instead of a filename-derived one.
Fixes#1635
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
0 commit comments