Le 2024-08-14 à 09 h 08, Konrad Windszus a écrit :
Module is a quite overloaded term so you always have to specify the context. For me module without the prefix “Java” doesn’t implicitly mean Java module. Same would apply for “package”. Is it Java package or Maven package (the lifecycle phase)?
We can not avoid all possible confusion. But we can reduce it. Maven does not really have the concept of modules. The elements that are inside the <module> elements are <project> elements. They are in separated POM files, but the root is always <project>. By using <subproject>, we reduce the <module> overload (even it does not eliminate it) and we get a more consistent naming: the content of a <subproject> is a <project>.
Martin
