Le 2025-05-15 à 18 h 52, Romain Manni-Bucau a écrit :
I didn't get why we can't get 1 artifact = 1 module so can stick to
current convention.
I presume that you mean "1 subproject = 1 module". It is still possible.
Nothing force users to abandon that model if they like it. "1 artifact =
1 module" is a different story, which will stay true if we consider that
"1 artifact = 1 JAR file".
We are making possible to use multi-modules projects possible, but *only
for users who want it*. The reasons have already been given on this
mailing list and on GitHub: multi-modules provide additional
compile-time safety (verification of references to dependent modules in
javadoc and in module `exports` and `opens` statements). It also
simplifies some tasks such as aggregated javadoc.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
