> On 16. Aug 2024, at 10:24, Christoph Läubrich <m...@laeubi-soft.de> wrote: > >> I would hence restrict the use of "sub-something" to inheritance (think >> "sub-class") and never use it to discussion aggregation. In particular, >> "submodule" is really redundant, as a module is always below an >> aggregator by definition.)
Actually, a module is just a relative path and can in fact go up. So the definition of "below" is not necessarily synonymous with "nested" or "inside". Wild suggestion... Instead of <modules> <module>a</module> <module>../b</module> </modules> use terminology that we know (e.g. aggregate) and re-use terminology from the parent element for relative project/POM references <aggregation> <relativePath>a</relativePath> <relativePath>../b</relativePath> </aggregation> -- Richard --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
