Hi Martin,
I would say the term module is totally fine. We have, as everywhere in
our human word, a lot of homonyms, everythere. The term module is as
good as project or component or even partition.
What is more imporant is to have a good definion of a term before using
it. So what is the definition of a Maven subproject and what there is it
documented.
And how to explain a junior dev why he must call it Maven subproject but
must write module. IMHO this would cause much more confusion then we all
would profit from it.
j2c,
Oliver
Am 05.08.24 um 14:14 schrieb Martin Desruisseaux:
In order to avoid confusion between "Maven module" and "Java module",
I suggest to update documentation for using "Maven sub-project"
instead of "Maven module". However, the <module> XML elements in the
POM would be unchanged for compatibility reason. There is apparently
not so many places in the documentation that need to be updated. The
ones that I found are part of pull request #1625:
https://github.com/apache/maven/pull/1625/commits/4bc46b4114396e6025645f3c5dae888f3d386981
Martin
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
