Le 27/08/2026 à 14:15, Romain Manni-Bucau a écrit :
Hmm, maybe I misread the diff but AFAIK current PR does only violate artifactId value by overriding it silently by the module id
No. When compiling a multi-module project, javac writes the output of each module in a directory having the module name (this is standard javac behavior, not something invented by the work on Maven module support). The pull request detects this situation and generates a JAR for each module. Because the result is many JAR files (one per module), we cannot use a single artifactID anymore. The name of each module is used as artifactID. The plugin also generates the corresponding pom.xml for each JAR.
inconsistencies with other plus (sources, javadoc etc - agree we could align them but also think we should stick to our model and not disrespect it).
We will need to align them, otherwise we cannot support multi-module in Java sense. It is already on my roadmap after JAR.
I'm also a bit worried on the coordinate -> file names vs java modules
File name is Java module name + version number and eventually other stuff (type, etc.) if we want.
Martin
