I very dislike the "module" terminology, which is not even reflected
in the code / api.  The API only has a notion of "Project".  The
notion of modules is only used while loading the reactor and never
used again after.  Everything is about "project" in maven, so I
disagree with Jeff Jensen.

I would also suggest making the modules xml bits optional and scan all
child directories for POMs by default if the project has a POM
packaging and no module explicitly specified.  You'd only have to
specify those if you want to enable module selection from profiles
(i.e. only have a subset of modules by default, and add others by
activating profiles).

So +1 for me.

Le lun. 5 août 2024 à 14:29, Jeff Jensen
<jeffjen...@upstairstechnology.com> a écrit :
>
> Additionally, since a module is part of a product and project is activity
> to change a product, I prefer the term "module" (or even "submodule")
> because they are not "projects" (yes Eclipse and other tools refer to them
> as "projects" but that is arguably a wrong term).  I also would rather
> clarify the module term with each use, Java Module and Maven Module, or use
> the term submodule for Maven modules.
>
>
> On Mon, Aug 5, 2024 at 7:23 AM Tamás Cservenák <ta...@cservenak.net> wrote:
>
> > Howdy,
> >
> > While I somewhat agree, I think that "Maven module" is clear when used in
> > context, also Maven was there before JPMS ;)
> > And finally, as you pointed out, POM will always have a "module" as well.
> > Hence, I am unsure about the value of this terminology change...
> > Yes, it is longer to type "maven module" and "java module" but it is still
> > clear what we talk about ...
> >
> > Thanks
> > T
> >
> > On Mon, Aug 5, 2024 at 2:14 PM Martin Desruisseaux <
> > martin.desruisse...@geomatys.com> wrote:
> >
> > > In order to avoid confusion between "Maven module" and "Java module", I
> > > suggest to update documentation for using "Maven sub-project" instead of
> > > "Maven module". However, the <module> XML elements in the POM would be
> > > unchanged for compatibility reason. There is apparently not so many
> > > places in the documentation that need to be updated. The ones that I
> > > found are part of pull request #1625:
> > >
> > >
> > >
> > https://github.com/apache/maven/pull/1625/commits/4bc46b4114396e6025645f3c5dae888f3d386981
> > >
> > >     Martin
> > >
> > >
> >



-- 
------------------------
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to