Re: Proposal: new default directory layout for modular project

Still in favor of #1 Le jeu. 15 mai 2025 à 18:26, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Hello all > > Currently, the default directory for source code in Maven 4 is: > > src/${scope}/${lang} > > Where ${scope} is "main" or "test" and ${lang} is "java" or "resourc

[ANN] Apache Maven Changes Plugin 3.0.0-M3 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Changes Plugin, version 3.0.0-M3 This plugin is used to inform your users of the changes that have occurred between different releases of your project. The plugin can extract these changes, either from a changes.xml file

[RESULT] [VOTE] Release Apache Maven Changes Plugin version 3.0.0-M3

Hi, The vote has passed with the following result: +1: Michael Osipov, Olivier Lamy, Slawomir Jaranowski, Sylwester Lachiewicz, Tamás Cservenák, Karl Heinz Marbaise PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central re

Re: [VOTE] Release Maven Resolver 2.0.9

+1 czw., 15 maj 2025, 22:54 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: > +1 > > On Thu, 15 May 2025 at 15:37, Tamás Cservenák wrote: > > > Howdy, > > > > This Resolver 2.0.9 release is a release with some bug fixes and > > improvements as well. > > > > Maven 4.x is picking

Re: Proposal: new default directory layout for modular project

Le 2025-05-15 à 22 h 02, Andy Law a écrit : I still think that the new folder structure feels “dirty”, and from my current position of ignorance, it also feels like the element under actually creates a problem that didn’t really exist. The goal of this JPMS work is to give more control to

Re: [VOTE] Release Maven Resolver 2.0.9

+1 On Thu, 15 May 2025 at 15:37, Tamás Cservenák wrote: > Howdy, > > This Resolver 2.0.9 release is a release with some bug fixes and > improvements as well. > > Maven 4.x is picking up Resolver 2.x, while Maven 3.x remains at > Resolver 1.x lineage. The two major versions, as far as client code

Re: Proposal: new default directory layout for modular project

> 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 th

Re: Proposal: new default directory layout for modular project

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 element under actually creates a problem

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 . If the process of building a set of JPMS module is different from that, then my suggestion to create a new type allows Maven to differentiate between a

Re: Proposal: new default directory layout for modular project

Le 2025-05-15 à 19 h 55, Sergey Chernov a écrit : Is "src/${scope}-${module}/${lang}" a considerable option? It wasn't mentioned in previous discussions on GitHub. I just added it as a 4th proposal in the wiki page.     Martin

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 type for JPM

Re: Proposal: new default directory layout for modular project

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 I apologise for not being clearer. Later, Andy From: Martin Desruisseaux Date: Thursday, 15 May 2025 at 19:24 To: dev@maven.apache.org Subject: Re: Pr

Re: Proposal: new default directory layout for modular project

Le 2025-05-15 à 19 h 54, Andy Law a écrit : Or maybe go the whole hog and define a new type specifically for jpms and just use the standard layouts underneath that? Does "standard layouts" means "layout defined by the javac man page"? If yes, the default layout is just "src/${module}", with

Re: Proposal: new default directory layout for modular project

Le 2025-05-15 à 19 h 39, Romain Manni-Bucau a écrit : I still fail why you need to not respect current maven layout, Because it doesn't work with multi-release compilation. you are allowed to enhance plugins to be inter maven modules if you want - tycho does it for years it adds layers of

Re: Proposal: new default directory layout for modular project

Hello David The usefulness of multi-modules compilation may be debated, but I don't think that Maven should impose its view on users. Multi-modules is a Java feature that exists, is documented, standardized and officially supported. It does provide some benefits. It may come at the cost of so

Re: Proposal: new default directory layout for modular project

Is "src/${scope}-${module}/${lang}" a considerable option? This may preserve classic file layout back compatibility when the module part is undefined. Also it will be alphabetically sortable in the filesystem (inside of src/ dir). On Thu, May 15, 2025 at 7:40 PM Romain Manni-Bucau wrote: > I sti

Re: Proposal: new default directory layout for modular project

Or maybe go the whole hog and define a new type specifically for jpms and just use the standard layouts underneath that? Later, Andy From: Romain Manni-Bucau Date: Thursday, 15 May 2025 at 18:42 To: Maven Developers List Subject: Re: Proposal: new default directory layout for modular project

Re: Proposal: new default directory layout for modular project

I still fail why you need to not respect current maven layout, you are allowed to enhance plugins to be inter maven modules if you want - tycho does it for years - and it would be more natural for maven land IMHO and enables JPMS for the few willing to use this mode, no? Romain Manni-Bucau @rmanni

Re: Proposal: new default directory layout for modular project

I'll start by saying that it definitely should not be 3, because you will not be able to tell by structure (for certain) whether a directory constitutes a module or whether it is some other kind of resource. As someone who has been at least somewhat involved with the JPMS since the beginning, and

Re: Proposal: new default directory layout for modular project

Le 2025-05-15 à 19 h 03, Andy Law a écrit : I don’t understand why this is so different from an aggregated project, with ${module} above src, but I may be missing the point because I’ve not spent any time thinking about JPMS yet. Because it enables compile-time verification that the compiler

Re: Proposal: new default directory layout for modular project

Le 2025-05-15 à 18 h 52, Romain Manni-Bucau a écrit : I didn't get why we can't get 1 artifact = 1 module so can stick to current convention. I presume that you mean "1 subproject = 1 module". It is still possible. Nothing force users to abandon that model if they like it. "1 artifact = 1 m

Re: Proposal: new default directory layout for modular project

I don’t understand why this is so different from an aggregated project, with ${module} above src, but I may be missing the point because I’ve not spent any time thinking about JPMS yet. You’re going to give me headaches navigating if you put ${module} anywhere below either ${scope} or ${lang} t

Re: Proposal: new default directory layout for modular project

Hi Martin, I didn't get why we can't get 1 artifact = 1 module so can stick to current convention. AFAIK maven always rejected multiple "main" artifacts/module even if we all do. Romain Manni-Bucau @rmannibucau | .NET Blog | Blog

Proposal: new default directory layout for modular project

Hello all Currently, the default directory for source code in Maven 4 is: src/${scope}/${lang} Where ${scope} is "main" or "test" and ${lang} is "java" or "resources". However, in the case of a multi-modules JPMS projects, we need to add the module name somewhere. Notes: * This change a

Re: [VOTE] Release Apache Maven Archetype version 3.4.0

+1 Karl Heinz Marbaise 于2025年5月15日 周四15:41写道： > Hi, > > +1 from me. > > Kind regards > Karl Heinz Marbaise > On 13.05.25 23:21, Slawomir Jaranowski wrote: > > Hi, > > > > We solved 32 issues: > > https://github.com/apache/maven-archetype/milestone/1?closed=1 > > > > There is one issues left in Gi

Re: [VOTE] Release Maven Resolver 2.0.9

+1 Tamás Cservenák 于2025年5月15日 周四21:34写道： > Howdy, > > This Resolver 2.0.9 release is a release with some bug fixes and > improvements as well. > > Maven 4.x is picking up Resolver 2.x, while Maven 3.x remains at > Resolver 1.x lineage. The two major versions, as far as client code > goes (Mojos

[VOTE] Release Maven Resolver 2.0.9

Howdy, This Resolver 2.0.9 release is a release with some bug fixes and improvements as well. Maven 4.x is picking up Resolver 2.x, while Maven 3.x remains at Resolver 1.x lineage. The two major versions, as far as client code goes (Mojos or extensions, using Resolver API as documented), are bina

Re: [VOTE] Release Apache Maven Archetype version 3.4.0

Hi, +1 from me. Kind regards Karl Heinz Marbaise On 13.05.25 23:21, Slawomir Jaranowski wrote: Hi, We solved 32 issues: https://github.com/apache/maven-archetype/milestone/1?closed=1 There is one issues left in GitHub: https://github.com/apache/maven-archetype/issues There are still a couple

Re: [VOTE] Release Apache Maven Changes Plugin version 3.0.0-M3

Hi, +1 from me. Kind regards Karl Heinz Marbaise On 12.05.25 21:15, Slawomir Jaranowski wrote: Hi, We solved 23 issues: https://github.com/apache/maven-changes-plugin/milestone/1?closed=1 There are no issues left in GitHub: https://github.com/apache/maven-changes-plugin/issues There are still

Re: [VOTE] Release Apache Maven Changes Plugin version 3.0.0-M3

+1 On Mon, May 12, 2025, 21:17 Slawomir Jaranowski wrote: > Hi, > > We solved 23 issues: > https://github.com/apache/maven-changes-plugin/milestone/1?closed=1 > > There are no issues left in GitHub: > https://github.com/apache/maven-changes-plugin/issues > > There are still a couple of issues le

Re: [VOTE] Release Apache Maven Archetype version 3.4.0

+1 czw., 15 maj 2025, 08:59 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: > +1 > > On Tue, 13 May 2025 at 23:21, Slawomir Jaranowski > wrote: > > > Hi, > > > > We solved 32 issues: > > https://github.com/apache/maven-archetype/milestone/1?closed=1 > > > > There is one issues

Re: [VOTE] Release Apache Maven Changes Plugin version 3.0.0-M3

+1 czw., 15 maj 2025, 08:59 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: > +1 > > On Mon, 12 May 2025 at 21:15, Slawomir Jaranowski > wrote: > > > Hi, > > > > We solved 23 issues: > > https://github.com/apache/maven-changes-plugin/milestone/1?closed=1 > > > > There are no is

Re: [VOTE] Release Apache Maven Archetype version 3.4.0

+1 On Tue, 13 May 2025 at 23:21, Slawomir Jaranowski wrote: > Hi, > > We solved 32 issues: > https://github.com/apache/maven-archetype/milestone/1?closed=1 > > There is one issues left in GitHub: > https://github.com/apache/maven-archetype/issues > > There are still a couple of issues left in JI