> But it seems to me that the Maven spirit is "1 subproject = 1 compilation task + closely related tasks for
not, a maven module defines an artifact (=gav + type if we want to be strict, others are additions), this is unrelated to anything java specific actually. If all your folders will end in the same jar your proposal is the way to go, else it goes against maven and updating the plugins sounds more logical in current model AFAIK. Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Le jeu. 15 mai 2025 à 22:02, Andy Law <andy....@roslin.ed.ac.uk> a écrit : > OK. I just re-read the first part of the wiki page with the detail of the > new child elements. Apologies, I had missed that bit. > > I still think that the new folder structure feels “dirty”, and from my > current position of ignorance, it also feels like the <module> element > under <source> actually creates a problem that didn’t really exist. Can > someone please point me towards the discussion behind the introduction of > that element so I can understand it better? > > Later, > > Andy > > From: Andy Law <andy....@roslin.ed.ac.uk> > Date: Thursday, 15 May 2025 at 20:44 > To: Maven Developers List <dev@maven.apache.org> > Subject: Re: Proposal: new default directory layout for modular project > 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 <martin.desruisse...@geomatys.com> > Date: Thursday, 15 May 2025 at 19:37 > To: dev@maven.apache.org <dev@maven.apache.org> > 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: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > 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. >
