Re: New Life Cycles Maven 4.0.0-rc3

I think thats agood idea and easy understandable by users. As already said by Maarten they know this by JUnit and others Von meinem iPhone gesendet > Am 18.03.2025 um 18:34 schrieb Guillaume Nodet : > > Yeha, we could add *each* in addition to the *all* phase. > >> Le mar. 18 mars 2025 à 15:1

[ANN] Apache Maven Parent POMs 44 Released

The Apache Maven team is pleased to announce the release of the Maven Parent POMs Version 44. https://maven.apache.org/pom/maven/ You should specify the version in your project as parent like the following: org.apache.maven maven-parent 44 You can download the appropriate sources etc. from th

[RESULT] [VOTE] Release Apache Maven Project Parent POMs version 44

Hi, The vote has passed with the following result: +1: Matthias Bünger, Sylwester Lachiewicz, Guillaume Nodet, Olivier Lamy, Karl Heinz Marbaise, Slawomir Jaranowski PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central r

[ANN] Apache Software Foundation Parent POM Version 34 Released

The Apache Maven team is pleased to announce the release of the Apache Software Foundation Parent POM Version, version 34 https://maven.apache.org/pom/asf/ You should specify the version in your project as parent like the following: org.apache apache 34 You can download the appropriate

[RESULT] [VOTE] Release Apache Software Foundation Parent POM version 34

Hi, The vote has passed with the following result: +1: Matthias Bünger, Sylwester Lachiewicz, Guillaume Nodet, Olivier Lamy, Karl Heinz Marbaise, Slawomir Jaranowski PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central r

Re: [VOTE] Release Apache Maven Project Parent POMs version 44

+1 On Sat, 15 Mar 2025 at 20:38, Slawomir Jaranowski wrote: > > Hi, > > NOTICE: > ASF Maven parent 34 from staging is required for testing. > > We solved 40 issues: > https://github.com/apache/maven-parent/milestone/5?closed=1 > > There are still a couple of issues left in GitHUb > https://github

Re: [VOTE] Release Apache Software Foundation Parent POM version 34

+1 On Sat, 15 Mar 2025 at 12:55, Slawomir Jaranowski wrote: > > Hi, > > We solved 39 issues: > https://github.com/apache/maven-apache-parent/milestone/5?closed=1 > > There are no issues in GitHub > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=pro

Re: BOM / Imported BOM - Maven 4.0.0-rc3

Howdy, Problem with BOM imports is that they were never "done done" in Maven 3.x time-frame, and they work the total opposite to everything else in Maven (think dependencies, as Delany says), hence they work in "non Maven way", not intuitive way, and tend to cause (usually bad) surprises. Sadly, t

Re: New Life Cycles Maven 4.0.0-rc3

Yeha, we could add *each* in addition to the *all* phase. Le mar. 18 mars 2025 à 15:18, Maarten Mulders a écrit : > Thinking out loud... would it make more sense to name those phases > "before:each" and "after:each" - following the vocabulary that e.g. > JUnit uses? > > > - Maarten > > On 18/03/

Re: New Life Cycles Maven 4.0.0-rc3

Hi, On 18.03.25 15:17, Maarten Mulders wrote: Thinking out loud... would it make more sense to name those phases "before:each" and "after:each" - following the vocabulary that e.g. JUnit uses? I already wrote something about that... Kind regards Karl Heinz Marbaise - Maarten On 18/03/2025

Re: New Life Cycles Maven 4.0.0-rc3

Thinking out loud... would it make more sense to name those phases "before:each" and "after:each" - following the vocabulary that e.g. JUnit uses? - Maarten On 18/03/2025 12:24, Guillaume Nodet wrote: The `all` phase is executed for each project. But you can avoid the plugin execution to be

Re: New Life Cycles Maven 4.0.0-rc3

The `all` phase is executed for each project. But you can avoid the plugin execution to be inherited by setting inherited="false" on the execution. I've spotted a bug I think, as the definition of this phase does not reference child projects, so they may not be executed at the correct time. Could

Re: [DISCUSS] Create Maven 4.0.x branch and switch to 4.1.0-SNAPSHOT

Le mar. 18 mars 2025 à 10:09, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Le 2025-03-18 à 09 h 57, Romain Manni-Bucau a écrit : > > > > Hmm, processor is not really a scope, more just a qualifier since it > > can be used for compile or test scopes and even worse, often > >

Re: Maven site plugin 4 documentation

This is actually what I did here: https://issues.apache.org/jira/projects/MSITE/versions/12354044, but I have no clue how to upgrade to Maven 4 APIs. On 2025/03/18 07:22:46 Hervé Boutemy wrote: > @michaelo I don't know how the plugin works with Maven 4, but perhaps we > should get to a state wh

Re: [DISCUSS] Create Maven 4.0.x branch and switch to 4.1.0-SNAPSHOT

Le 2025-03-18 à 09 h 57, Romain Manni-Bucau a écrit : Hmm, processor is not really a scope, more just a qualifier since it can be used for compile or test scopes and even worse, often processors are provided scope (maybe as a workaround to avoid optional but still a thing in current maven pic

Re: [DISCUSS] Create Maven 4.0.x branch and switch to 4.1.0-SNAPSHOT

Hmm, processor is not really a scope, more just a qualifier since it can be used for compile or test scopes and even worse, often processors are provided scope (maybe as a workaround to avoid optional but still a thing in current maven picture). Romain Manni-Bucau @rmannibucau

Re: [DISCUSS] Create Maven 4.0.x branch and switch to 4.1.0-SNAPSHOT

Le 2025-03-18 à 08 h 05, Thomas Reinhardt a écrit : On 17/03/2025 17:03, Matthias Bünger wrote: I'm not an IDE developer, but Maven user and mixing those two, for me independend things, will make it more confusing than simpler. Spot on. Please don't mix those. Because we will end up either with

Re: BOM / Imported BOM - Maven 4.0.0-rc3

Hi, AFAIK bom import never worked when there was overlapping dependencies (never worked = it can work but it was not defined and behavior was not guaranteed nor intended by design). What works better from my experience is to not use the import scope and rather just the type=pom with a proper scope

Re: Maven site plugin 4 documentation

@michaelo I don't know how the plugin works with Maven 4, but perhaps we should get to a state where we can release Maven Site Plugin 4.0.0-alpha1 or beta1, so the milestones series (not Maven 4 but Doxia 2) is not seen by end users any more => less confusion Le mardi 18 mars 2025, 07:55:41 CET

Re: [DISCUSS] Create Maven 4.0.x branch and switch to 4.1.0-SNAPSHOT

On 17/03/2025 17:03, Matthias Bünger wrote: I'm not an IDE developer, but Maven user and mixing those two, for me independend things, will make it more confusing than simpler. Spot on. Please don't mix those. Because we will end up either with limited options or an explosion of all valid com