I agree this is a problem. Not the first time that a new Java language feature has caused problems for much existing code. Who else remembers that JUnit's assertTrue used to be simply assert? That was an ugly one.
In this case, I'm not yet sold that the cure isn't worse than the disease. In particular I'm not sure a change in the pom format is justified. There's too much existing code, documentation, tooling, and, most importantly, knowledge inside developers' heads to make this change pain free. If we were starting from a green field, then this would certainly make sense, but since we're not I think there'll be less pain by sticking with the status quo. On Mon, Aug 5, 2024 at 8:14 AM 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 > -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
