I must be missing something here. It’s already perfectly possible to manage and build multi-module projects using an aggregator pom file and <modules>. If the process of building a set of JPMS module is different from that, then my suggestion to create a new <packaging> type allows Maven to differentiate between aggregated modules and multi-module JPMS projects and behave appropriately.
That seems much cleaner to me than forcing a new folder structure into the picture. That just feels “dirty”. Later, Andy From: Martin Desruisseaux <[email protected]> Date: Thursday, 15 May 2025 at 19:37 To: [email protected] <[email protected]> Subject: Re: Proposal: new default directory layout for modular project Le 2025-05-15 à 20 h 26, Andy Law a écrit : > > I confess that I was using “standard” in the context of what I > understand to be the _Maven_ standard, since this is the Maven > developers list > The core issue is that we need a different directory for each module. I don't see how a new <packaging> type for JPMS would resolve that, unless the proposal is that Maven aggregates all subprojects having that specific packaging type and compile them together, a little bit like aggregated javadoc. But it seems to me that the Maven spirit is "1 subproject = 1 compilation task + closely related tasks for multi-releases and tests", and that aggregated Javadoc is a hack that we should not reproduce as much as possible. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
