Re: [HEADS UP] Maven 3.9.10 release

[Sergey Chernov]

I discovered a problem. If the maven command has a module filter (-pl), the
build hangs in the very beginning. This is a reproducible problem on a
private project (about 700 modules) and obviously related to switch from
3.9.9 to 3.9.10-SNAPSHOT.

The gist with stack traces:
https://gist.github.com/seregamorph/31165de31a498c5b009353ea6a70d0d1

I tried to reproduce it on a smaller project (and even quarkus build), but
could not do it fast. Let me know if you need a reproducing project (this
will take some time).

On the first sight it looks like it falls into a trap of infinite cycle
around recursive applyFilter calls. This does not happen if there is no
module filter in the maven command.

On Mon, May 26, 2025 at 4:05 PM Slawomir Jaranowski 
wrote:

> Hi,
>
> For easy testing I have published latest version at:
>
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
>
> The same distribution will be done during releases.
>
>
> On Mon, 26 May 2025 at 15:45, Tamás Cservenák  wrote:
>
> > This is "CI build", which does NOT contain the version.
> > Reason for it is this:
> > https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> > The `-PversionlessMavenDist`. By the way, master does not use this
> > anymore as it just creates a mixup like this one...
> >
> > Thanks
> > T
> >
> > On Mon, May 26, 2025 at 3:27 PM James Gao  wrote:
> > >
> > > I think we should not change the archive folder structure in a patch
> > > release, and rollback to the previous name before GA.
> > >
> > > On Mon, May 26, 2025 at 9:09 PM James Gao  wrote:
> > >
> > > > @Sergey , the top folder name inside the zip file is different:
> > > > 3.9.9: folder name is "apache-maven-3.9.9/"
> > > > 3.9.10: folder name is "apache-maven/"
> > > > so the script breaks since the folder pattern is changed.
> > > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> Sławomir Jaranowski
>

Re: [HEADS UP] Maven 3.9.10 release

[Tamás Cservenák]

Seems related to this:
https://issues.apache.org/jira/browse/MNG-8256

Interestingly, this is not noticeable on master, we may have missed
some backport maybe?

Thanks
T

On Mon, May 26, 2025 at 5:45 PM Sergey Chernov  wrote:
>
> I discovered a problem. If the maven command has a module filter (-pl), the
> build hangs in the very beginning. This is a reproducible problem on a
> private project (about 700 modules) and obviously related to switch from
> 3.9.9 to 3.9.10-SNAPSHOT.
>
> The gist with stack traces:
> https://gist.github.com/seregamorph/31165de31a498c5b009353ea6a70d0d1
>
> I tried to reproduce it on a smaller project (and even quarkus build), but
> could not do it fast. Let me know if you need a reproducing project (this
> will take some time).
>
> On the first sight it looks like it falls into a trap of infinite cycle
> around recursive applyFilter calls. This does not happen if there is no
> module filter in the maven command.
>
> On Mon, May 26, 2025 at 4:05 PM Slawomir Jaranowski 
> wrote:
>
> > Hi,
> >
> > For easy testing I have published latest version at:
> >
> > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
> >
> > The same distribution will be done during releases.
> >
> >
> > On Mon, 26 May 2025 at 15:45, Tamás Cservenák  wrote:
> >
> > > This is "CI build", which does NOT contain the version.
> > > Reason for it is this:
> > > https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> > > The `-PversionlessMavenDist`. By the way, master does not use this
> > > anymore as it just creates a mixup like this one...
> > >
> > > Thanks
> > > T
> > >
> > > On Mon, May 26, 2025 at 3:27 PM James Gao  wrote:
> > > >
> > > > I think we should not change the archive folder structure in a patch
> > > > release, and rollback to the previous name before GA.
> > > >
> > > > On Mon, May 26, 2025 at 9:09 PM James Gao  wrote:
> > > >
> > > > > @Sergey , the top folder name inside the zip file is different:
> > > > > 3.9.9: folder name is "apache-maven-3.9.9/"
> > > > > 3.9.10: folder name is "apache-maven/"
> > > > > so the script breaks since the folder pattern is changed.
> > > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
> > --
> > Sławomir Jaranowski
> >

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

Re: [HEADS UP] Maven 3.9.10 release

[Tamás Cservenák]

Yup,
this went into master only:
https://issues.apache.org/jira/browse/MNG-8396
https://github.com/cstamas/maven/commit/62f85a4233366064750079d50fd86ef25a97c6f3

On Mon, May 26, 2025 at 6:57 PM Tamás Cservenák  wrote:
>
> Seems related to this:
> https://issues.apache.org/jira/browse/MNG-8256
>
> Interestingly, this is not noticeable on master, we may have missed
> some backport maybe?
>
> Thanks
> T
>
> On Mon, May 26, 2025 at 5:45 PM Sergey Chernov  wrote:
> >
> > I discovered a problem. If the maven command has a module filter (-pl), the
> > build hangs in the very beginning. This is a reproducible problem on a
> > private project (about 700 modules) and obviously related to switch from
> > 3.9.9 to 3.9.10-SNAPSHOT.
> >
> > The gist with stack traces:
> > https://gist.github.com/seregamorph/31165de31a498c5b009353ea6a70d0d1
> >
> > I tried to reproduce it on a smaller project (and even quarkus build), but
> > could not do it fast. Let me know if you need a reproducing project (this
> > will take some time).
> >
> > On the first sight it looks like it falls into a trap of infinite cycle
> > around recursive applyFilter calls. This does not happen if there is no
> > module filter in the maven command.
> >
> > On Mon, May 26, 2025 at 4:05 PM Slawomir Jaranowski 
> > wrote:
> >
> > > Hi,
> > >
> > > For easy testing I have published latest version at:
> > >
> > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
> > >
> > > The same distribution will be done during releases.
> > >
> > >
> > > On Mon, 26 May 2025 at 15:45, Tamás Cservenák  wrote:
> > >
> > > > This is "CI build", which does NOT contain the version.
> > > > Reason for it is this:
> > > > https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> > > > The `-PversionlessMavenDist`. By the way, master does not use this
> > > > anymore as it just creates a mixup like this one...
> > > >
> > > > Thanks
> > > > T
> > > >
> > > > On Mon, May 26, 2025 at 3:27 PM James Gao  wrote:
> > > > >
> > > > > I think we should not change the archive folder structure in a patch
> > > > > release, and rollback to the previous name before GA.
> > > > >
> > > > > On Mon, May 26, 2025 at 9:09 PM James Gao  wrote:
> > > > >
> > > > > > @Sergey , the top folder name inside the zip file is different:
> > > > > > 3.9.9: folder name is "apache-maven-3.9.9/"
> > > > > > 3.9.10: folder name is "apache-maven/"
> > > > > > so the script breaks since the folder pattern is changed.
> > > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >
> > > >
> > >
> > > --
> > > Sławomir Jaranowski
> > >

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

Re: [HEADS UP] Maven 3.9.10 release

[Michael Bien]

ran the NetBeans maven tooling integration tests against the snapshot and 
everything worked fine.

https://github.com/apache/netbeans/pull/8534

best regards,
michael

On 5/26/25 16:03, Slawomir Jaranowski wrote:
> Hi,
>
> For easy testing I have published latest version at:
>
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
>
> The same distribution will be done during releases.
>
>
> On Mon, 26 May 2025 at 15:45, Tamás Cservenák  wrote:
>
>> This is "CI build", which does NOT contain the version.
>> Reason for it is this:
>> https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
>> The `-PversionlessMavenDist`. By the way, master does not use this
>> anymore as it just creates a mixup like this one...
>>
>> Thanks
>> T
>>
>> On Mon, May 26, 2025 at 3:27 PM James Gao  wrote:
>>> I think we should not change the archive folder structure in a patch
>>> release, and rollback to the previous name before GA.
>>>
>>> On Mon, May 26, 2025 at 9:09 PM James Gao  wrote:
>>>
 @Sergey , the top folder name inside the zip file is different:
 3.9.9: folder name is "apache-maven-3.9.9/"
 3.9.10: folder name is "apache-maven/"
 so the script breaks since the folder pattern is changed.

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


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

Re: [HEADS UP] Maven 3.9.10 release

[Tamás Cservenák]

Created https://github.com/apache/maven/pull/2393

@Slawomir Jaranowski @Guillaume Nodet pls eyeball

On Mon, May 26, 2025 at 6:59 PM Tamás Cservenák  wrote:
>
> Yup,
> this went into master only:
> https://issues.apache.org/jira/browse/MNG-8396
> https://github.com/cstamas/maven/commit/62f85a4233366064750079d50fd86ef25a97c6f3
>
> On Mon, May 26, 2025 at 6:57 PM Tamás Cservenák  wrote:
> >
> > Seems related to this:
> > https://issues.apache.org/jira/browse/MNG-8256
> >
> > Interestingly, this is not noticeable on master, we may have missed
> > some backport maybe?
> >
> > Thanks
> > T
> >
> > On Mon, May 26, 2025 at 5:45 PM Sergey Chernov  
> > wrote:
> > >
> > > I discovered a problem. If the maven command has a module filter (-pl), 
> > > the
> > > build hangs in the very beginning. This is a reproducible problem on a
> > > private project (about 700 modules) and obviously related to switch from
> > > 3.9.9 to 3.9.10-SNAPSHOT.
> > >
> > > The gist with stack traces:
> > > https://gist.github.com/seregamorph/31165de31a498c5b009353ea6a70d0d1
> > >
> > > I tried to reproduce it on a smaller project (and even quarkus build), but
> > > could not do it fast. Let me know if you need a reproducing project (this
> > > will take some time).
> > >
> > > On the first sight it looks like it falls into a trap of infinite cycle
> > > around recursive applyFilter calls. This does not happen if there is no
> > > module filter in the maven command.
> > >
> > > On Mon, May 26, 2025 at 4:05 PM Slawomir Jaranowski 
> > > 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > For easy testing I have published latest version at:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
> > > >
> > > > The same distribution will be done during releases.
> > > >
> > > >
> > > > On Mon, 26 May 2025 at 15:45, Tamás Cservenák  
> > > > wrote:
> > > >
> > > > > This is "CI build", which does NOT contain the version.
> > > > > Reason for it is this:
> > > > > https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> > > > > The `-PversionlessMavenDist`. By the way, master does not use this
> > > > > anymore as it just creates a mixup like this one...
> > > > >
> > > > > Thanks
> > > > > T
> > > > >
> > > > > On Mon, May 26, 2025 at 3:27 PM James Gao  wrote:
> > > > > >
> > > > > > I think we should not change the archive folder structure in a patch
> > > > > > release, and rollback to the previous name before GA.
> > > > > >
> > > > > > On Mon, May 26, 2025 at 9:09 PM James Gao  wrote:
> > > > > >
> > > > > > > @Sergey , the top folder name inside the zip file is different:
> > > > > > > 3.9.9: folder name is "apache-maven-3.9.9/"
> > > > > > > 3.9.10: folder name is "apache-maven/"
> > > > > > > so the script breaks since the folder pattern is changed.
> > > > > > >
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > >
> > > > >
> > > >
> > > > --
> > > > Sławomir Jaranowski
> > > >

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

Re: [HEADS UP] Maven 3.9.10 release

[Sergey Chernov]

I built a commit from your fork and tried the build with filtering. It's
still hanging (the problem is not addressed).
```

commit 5b37f4eacfa25e81545650f292c8ea0d00035512 (HEAD,
cstamas/maven-3.9.x-MNG-8396)

Author: Tamas Cservenak 

Date:   Mon May 26 19:07:59 2025 +0200


[MNG-8396] Backport: add cache layer to the filtered dep graph



Backport of 62f85a4233366064750079d50fd86ef25a97c6f3
```

mvn -DdistributionTargetDir="$HOME/Java/apache-maven-3.9.x-SNAPSHOT" clean
package -DskipTests=true

...

# in the project

/Users/username/Java/apache-maven-3.9.x-SNAPSHOT/bin/mvn clean install
-DskipTests=true -pl :API


[INFO] Error stacktraces are turned on.

[INFO] Scanning for projects...

(hangs)




On Mon, May 26, 2025 at 7:12 PM Tamás Cservenák  wrote:

> Created https://github.com/apache/maven/pull/2393
>
> @Slawomir Jaranowski @Guillaume Nodet pls eyeball
>
> On Mon, May 26, 2025 at 6:59 PM Tamás Cservenák 
> wrote:
> >
> > Yup,
> > this went into master only:
> > https://issues.apache.org/jira/browse/MNG-8396
> >
> https://github.com/cstamas/maven/commit/62f85a4233366064750079d50fd86ef25a97c6f3
> >
> > On Mon, May 26, 2025 at 6:57 PM Tamás Cservenák 
> wrote:
> > >
> > > Seems related to this:
> > > https://issues.apache.org/jira/browse/MNG-8256
> > >
> > > Interestingly, this is not noticeable on master, we may have missed
> > > some backport maybe?
> > >
> > > Thanks
> > > T
> > >
> > > On Mon, May 26, 2025 at 5:45 PM Sergey Chernov 
> wrote:
> > > >
> > > > I discovered a problem. If the maven command has a module filter
> (-pl), the
> > > > build hangs in the very beginning. This is a reproducible problem on
> a
> > > > private project (about 700 modules) and obviously related to switch
> from
> > > > 3.9.9 to 3.9.10-SNAPSHOT.
> > > >
> > > > The gist with stack traces:
> > > > https://gist.github.com/seregamorph/31165de31a498c5b009353ea6a70d0d1
> > > >
> > > > I tried to reproduce it on a smaller project (and even quarkus
> build), but
> > > > could not do it fast. Let me know if you need a reproducing project
> (this
> > > > will take some time).
> > > >
> > > > On the first sight it looks like it falls into a trap of infinite
> cycle
> > > > around recursive applyFilter calls. This does not happen if there is
> no
> > > > module filter in the maven command.
> > > >
> > > > On Mon, May 26, 2025 at 4:05 PM Slawomir Jaranowski <
> s.jaranow...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > For easy testing I have published latest version at:
> > > > >
> > > > >
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
> > > > >
> > > > > The same distribution will be done during releases.
> > > > >
> > > > >
> > > > > On Mon, 26 May 2025 at 15:45, Tamás Cservenák 
> wrote:
> > > > >
> > > > > > This is "CI build", which does NOT contain the version.
> > > > > > Reason for it is this:
> > > > > > https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> > > > > > The `-PversionlessMavenDist`. By the way, master does not use
> this
> > > > > > anymore as it just creates a mixup like this one...
> > > > > >
> > > > > > Thanks
> > > > > > T
> > > > > >
> > > > > > On Mon, May 26, 2025 at 3:27 PM James Gao 
> wrote:
> > > > > > >
> > > > > > > I think we should not change the archive folder structure in a
> patch
> > > > > > > release, and rollback to the previous name before GA.
> > > > > > >
> > > > > > > On Mon, May 26, 2025 at 9:09 PM James Gao 
> wrote:
> > > > > > >
> > > > > > > > @Sergey , the top folder name inside the zip file is
> different:
> > > > > > > > 3.9.9: folder name is "apache-maven-3.9.9/"
> > > > > > > > 3.9.10: folder name is "apache-maven/"
> > > > > > > > so the script breaks since the folder pattern is changed.
> > > > > > > >
> > > > > >
> > > > > >
> -
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Sławomir Jaranowski
> > > > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [HEADS UP] Maven 3.9.10 release

[Tamás Cservenák]

Sergey, I added another commit, you missed.

T

On Mon, May 26, 2025 at 7:33 PM Sergey Chernov  wrote:
>
> I built a commit from your fork and tried the build with filtering. It's
> still hanging (the problem is not addressed).
> ```
>
> commit 5b37f4eacfa25e81545650f292c8ea0d00035512 (HEAD,
> cstamas/maven-3.9.x-MNG-8396)
>
> Author: Tamas Cservenak 
>
> Date:   Mon May 26 19:07:59 2025 +0200
>
>
> [MNG-8396] Backport: add cache layer to the filtered dep graph
>
>
>
> Backport of 62f85a4233366064750079d50fd86ef25a97c6f3
> ```
>
> mvn -DdistributionTargetDir="$HOME/Java/apache-maven-3.9.x-SNAPSHOT" clean
> package -DskipTests=true
>
> ...
>
> # in the project
>
> /Users/username/Java/apache-maven-3.9.x-SNAPSHOT/bin/mvn clean install
> -DskipTests=true -pl :API
>
>
> [INFO] Error stacktraces are turned on.
>
> [INFO] Scanning for projects...
>
> (hangs)
>
>
>
>
> On Mon, May 26, 2025 at 7:12 PM Tamás Cservenák  wrote:
>
> > Created https://github.com/apache/maven/pull/2393
> >
> > @Slawomir Jaranowski @Guillaume Nodet pls eyeball
> >
> > On Mon, May 26, 2025 at 6:59 PM Tamás Cservenák 
> > wrote:
> > >
> > > Yup,
> > > this went into master only:
> > > https://issues.apache.org/jira/browse/MNG-8396
> > >
> > https://github.com/cstamas/maven/commit/62f85a4233366064750079d50fd86ef25a97c6f3
> > >
> > > On Mon, May 26, 2025 at 6:57 PM Tamás Cservenák 
> > wrote:
> > > >
> > > > Seems related to this:
> > > > https://issues.apache.org/jira/browse/MNG-8256
> > > >
> > > > Interestingly, this is not noticeable on master, we may have missed
> > > > some backport maybe?
> > > >
> > > > Thanks
> > > > T
> > > >
> > > > On Mon, May 26, 2025 at 5:45 PM Sergey Chernov 
> > wrote:
> > > > >
> > > > > I discovered a problem. If the maven command has a module filter
> > (-pl), the
> > > > > build hangs in the very beginning. This is a reproducible problem on
> > a
> > > > > private project (about 700 modules) and obviously related to switch
> > from
> > > > > 3.9.9 to 3.9.10-SNAPSHOT.
> > > > >
> > > > > The gist with stack traces:
> > > > > https://gist.github.com/seregamorph/31165de31a498c5b009353ea6a70d0d1
> > > > >
> > > > > I tried to reproduce it on a smaller project (and even quarkus
> > build), but
> > > > > could not do it fast. Let me know if you need a reproducing project
> > (this
> > > > > will take some time).
> > > > >
> > > > > On the first sight it looks like it falls into a trap of infinite
> > cycle
> > > > > around recursive applyFilter calls. This does not happen if there is
> > no
> > > > > module filter in the maven command.
> > > > >
> > > > > On Mon, May 26, 2025 at 4:05 PM Slawomir Jaranowski <
> > s.jaranow...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > For easy testing I have published latest version at:
> > > > > >
> > > > > >
> > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
> > > > > >
> > > > > > The same distribution will be done during releases.
> > > > > >
> > > > > >
> > > > > > On Mon, 26 May 2025 at 15:45, Tamás Cservenák 
> > wrote:
> > > > > >
> > > > > > > This is "CI build", which does NOT contain the version.
> > > > > > > Reason for it is this:
> > > > > > > https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> > > > > > > The `-PversionlessMavenDist`. By the way, master does not use
> > this
> > > > > > > anymore as it just creates a mixup like this one...
> > > > > > >
> > > > > > > Thanks
> > > > > > > T
> > > > > > >
> > > > > > > On Mon, May 26, 2025 at 3:27 PM James Gao 
> > wrote:
> > > > > > > >
> > > > > > > > I think we should not change the archive folder structure in a
> > patch
> > > > > > > > release, and rollback to the previous name before GA.
> > > > > > > >
> > > > > > > > On Mon, May 26, 2025 at 9:09 PM James Gao 
> > wrote:
> > > > > > > >
> > > > > > > > > @Sergey , the top folder name inside the zip file is
> > different:
> > > > > > > > > 3.9.9: folder name is "apache-maven-3.9.9/"
> > > > > > > > > 3.9.10: folder name is "apache-maven/"
> > > > > > > > > so the script breaks since the folder pattern is changed.
> > > > > > > > >
> > > > > > >
> > > > > > >
> > -
> > > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Sławomir Jaranowski
> > > > > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >

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

Re: [HEADS UP] Maven 3.9.10 release

[Sergey Chernov]

Seems to be ok now 👍


On Mon, May 26, 2025 at 7:37 PM Tamás Cservenák  wrote:

> Sergey, I added another commit, you missed.
>
> T
>
> On Mon, May 26, 2025 at 7:33 PM Sergey Chernov 
> wrote:
> >
> > I built a commit from your fork and tried the build with filtering. It's
> > still hanging (the problem is not addressed).
> > ```
> >
> > commit 5b37f4eacfa25e81545650f292c8ea0d00035512 (HEAD,
> > cstamas/maven-3.9.x-MNG-8396)
> >
> > Author: Tamas Cservenak 
> >
> > Date:   Mon May 26 19:07:59 2025 +0200
> >
> >
> > [MNG-8396] Backport: add cache layer to the filtered dep graph
> >
> >
> >
> > Backport of 62f85a4233366064750079d50fd86ef25a97c6f3
> > ```
> >
> > mvn -DdistributionTargetDir="$HOME/Java/apache-maven-3.9.x-SNAPSHOT"
> clean
> > package -DskipTests=true
> >
> > ...
> >
> > # in the project
> >
> > /Users/username/Java/apache-maven-3.9.x-SNAPSHOT/bin/mvn clean install
> > -DskipTests=true -pl :API
> >
> >
> > [INFO] Error stacktraces are turned on.
> >
> > [INFO] Scanning for projects...
> >
> > (hangs)
> >
> >
> >
> >
> > On Mon, May 26, 2025 at 7:12 PM Tamás Cservenák 
> wrote:
> >
> > > Created https://github.com/apache/maven/pull/2393
> > >
> > > @Slawomir Jaranowski @Guillaume Nodet pls eyeball
> > >
> > > On Mon, May 26, 2025 at 6:59 PM Tamás Cservenák 
> > > wrote:
> > > >
> > > > Yup,
> > > > this went into master only:
> > > > https://issues.apache.org/jira/browse/MNG-8396
> > > >
> > >
> https://github.com/cstamas/maven/commit/62f85a4233366064750079d50fd86ef25a97c6f3
> > > >
> > > > On Mon, May 26, 2025 at 6:57 PM Tamás Cservenák  >
> > > wrote:
> > > > >
> > > > > Seems related to this:
> > > > > https://issues.apache.org/jira/browse/MNG-8256
> > > > >
> > > > > Interestingly, this is not noticeable on master, we may have missed
> > > > > some backport maybe?
> > > > >
> > > > > Thanks
> > > > > T
> > > > >
> > > > > On Mon, May 26, 2025 at 5:45 PM Sergey Chernov <
> serega.mo...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > I discovered a problem. If the maven command has a module filter
> > > (-pl), the
> > > > > > build hangs in the very beginning. This is a reproducible
> problem on
> > > a
> > > > > > private project (about 700 modules) and obviously related to
> switch
> > > from
> > > > > > 3.9.9 to 3.9.10-SNAPSHOT.
> > > > > >
> > > > > > The gist with stack traces:
> > > > > >
> https://gist.github.com/seregamorph/31165de31a498c5b009353ea6a70d0d1
> > > > > >
> > > > > > I tried to reproduce it on a smaller project (and even quarkus
> > > build), but
> > > > > > could not do it fast. Let me know if you need a reproducing
> project
> > > (this
> > > > > > will take some time).
> > > > > >
> > > > > > On the first sight it looks like it falls into a trap of infinite
> > > cycle
> > > > > > around recursive applyFilter calls. This does not happen if
> there is
> > > no
> > > > > > module filter in the maven command.
> > > > > >
> > > > > > On Mon, May 26, 2025 at 4:05 PM Slawomir Jaranowski <
> > > s.jaranow...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > For easy testing I have published latest version at:
> > > > > > >
> > > > > > >
> > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
> > > > > > >
> > > > > > > The same distribution will be done during releases.
> > > > > > >
> > > > > > >
> > > > > > > On Mon, 26 May 2025 at 15:45, Tamás Cservenák <
> ta...@cservenak.net>
> > > wrote:
> > > > > > >
> > > > > > > > This is "CI build", which does NOT contain the version.
> > > > > > > > Reason for it is this:
> > > > > > > >
> https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> > > > > > > > The `-PversionlessMavenDist`. By the way, master does not use
> > > this
> > > > > > > > anymore as it just creates a mixup like this one...
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > > T
> > > > > > > >
> > > > > > > > On Mon, May 26, 2025 at 3:27 PM James Gao  >
> > > wrote:
> > > > > > > > >
> > > > > > > > > I think we should not change the archive folder structure
> in a
> > > patch
> > > > > > > > > release, and rollback to the previous name before GA.
> > > > > > > > >
> > > > > > > > > On Mon, May 26, 2025 at 9:09 PM James Gao <
> gaoz...@gmail.com>
> > > wrote:
> > > > > > > > >
> > > > > > > > > > @Sergey , the top folder name inside the zip file is
> > > different:
> > > > > > > > > > 3.9.9: folder name is "apache-maven-3.9.9/"
> > > > > > > > > > 3.9.10: folder name is "apache-maven/"
> > > > > > > > > > so the script breaks since the folder pattern is changed.
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > -
> > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Sławomir Jaranowski
> > > > > > >
> > >
> > > 

Re: [HEADS UP] Maven 3.9.10 release

[Slawomir Jaranowski]

dev distribution updated:

https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
svnid: 77141

Apache Maven 3.9.10-SNAPSHOT (1da6ce51230b0b3247c983ec25bdeae21d52395f)


On Mon, 26 May 2025 at 19:48, Sergey Chernov  wrote:

> Seems to be ok now 👍
>
>
> On Mon, May 26, 2025 at 7:37 PM Tamás Cservenák 
> wrote:
>
> > Sergey, I added another commit, you missed.
> >
> > T
> >
> > On Mon, May 26, 2025 at 7:33 PM Sergey Chernov 
> > wrote:
> > >
> > > I built a commit from your fork and tried the build with filtering.
> It's
> > > still hanging (the problem is not addressed).
> > > ```
> > >
> > > commit 5b37f4eacfa25e81545650f292c8ea0d00035512 (HEAD,
> > > cstamas/maven-3.9.x-MNG-8396)
> > >
> > > Author: Tamas Cservenak 
> > >
> > > Date:   Mon May 26 19:07:59 2025 +0200
> > >
> > >
> > > [MNG-8396] Backport: add cache layer to the filtered dep graph
> > >
> > >
> > >
> > > Backport of 62f85a4233366064750079d50fd86ef25a97c6f3
> > > ```
> > >
> > > mvn -DdistributionTargetDir="$HOME/Java/apache-maven-3.9.x-SNAPSHOT"
> > clean
> > > package -DskipTests=true
> > >
> > > ...
> > >
> > > # in the project
> > >
> > > /Users/username/Java/apache-maven-3.9.x-SNAPSHOT/bin/mvn clean install
> > > -DskipTests=true -pl :API
> > >
> > >
> > > [INFO] Error stacktraces are turned on.
> > >
> > > [INFO] Scanning for projects...
> > >
> > > (hangs)
> > >
> > >
> > >
> > >
> > > On Mon, May 26, 2025 at 7:12 PM Tamás Cservenák 
> > wrote:
> > >
> > > > Created https://github.com/apache/maven/pull/2393
> > > >
> > > > @Slawomir Jaranowski @Guillaume Nodet pls eyeball
> > > >
> > > > On Mon, May 26, 2025 at 6:59 PM Tamás Cservenák  >
> > > > wrote:
> > > > >
> > > > > Yup,
> > > > > this went into master only:
> > > > > https://issues.apache.org/jira/browse/MNG-8396
> > > > >
> > > >
> >
> https://github.com/cstamas/maven/commit/62f85a4233366064750079d50fd86ef25a97c6f3
> > > > >
> > > > > On Mon, May 26, 2025 at 6:57 PM Tamás Cservenák <
> ta...@cservenak.net
> > >
> > > > wrote:
> > > > > >
> > > > > > Seems related to this:
> > > > > > https://issues.apache.org/jira/browse/MNG-8256
> > > > > >
> > > > > > Interestingly, this is not noticeable on master, we may have
> missed
> > > > > > some backport maybe?
> > > > > >
> > > > > > Thanks
> > > > > > T
> > > > > >
> > > > > > On Mon, May 26, 2025 at 5:45 PM Sergey Chernov <
> > serega.mo...@gmail.com>
> > > > wrote:
> > > > > > >
> > > > > > > I discovered a problem. If the maven command has a module
> filter
> > > > (-pl), the
> > > > > > > build hangs in the very beginning. This is a reproducible
> > problem on
> > > > a
> > > > > > > private project (about 700 modules) and obviously related to
> > switch
> > > > from
> > > > > > > 3.9.9 to 3.9.10-SNAPSHOT.
> > > > > > >
> > > > > > > The gist with stack traces:
> > > > > > >
> > https://gist.github.com/seregamorph/31165de31a498c5b009353ea6a70d0d1
> > > > > > >
> > > > > > > I tried to reproduce it on a smaller project (and even quarkus
> > > > build), but
> > > > > > > could not do it fast. Let me know if you need a reproducing
> > project
> > > > (this
> > > > > > > will take some time).
> > > > > > >
> > > > > > > On the first sight it looks like it falls into a trap of
> infinite
> > > > cycle
> > > > > > > around recursive applyFilter calls. This does not happen if
> > there is
> > > > no
> > > > > > > module filter in the maven command.
> > > > > > >
> > > > > > > On Mon, May 26, 2025 at 4:05 PM Slawomir Jaranowski <
> > > > s.jaranow...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > For easy testing I have published latest version at:
> > > > > > > >
> > > > > > > >
> > > >
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/
> > > > > > > >
> > > > > > > > The same distribution will be done during releases.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, 26 May 2025 at 15:45, Tamás Cservenák <
> > ta...@cservenak.net>
> > > > wrote:
> > > > > > > >
> > > > > > > > > This is "CI build", which does NOT contain the version.
> > > > > > > > > Reason for it is this:
> > > > > > > > >
> > https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> > > > > > > > > The `-PversionlessMavenDist`. By the way, master does not
> use
> > > > this
> > > > > > > > > anymore as it just creates a mixup like this one...
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > > T
> > > > > > > > >
> > > > > > > > > On Mon, May 26, 2025 at 3:27 PM James Gao <
> gaoz...@gmail.com
> > >
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > I think we should not change the archive folder structure
> > in a
> > > > patch
> > > > > > > > > > release, and rollback to the previous name before GA.
> > > > > > > > > >
> > > > > > > > > > On Mon, May 26, 2025 at 9:09 PM James Gao <
> > gaoz...@gmail.com>
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > @Sergey , the top folder name inside the zip file is
> > > > different:
> > > > > 

Re: Maven 4.0.0 Release - Thoughts?

[Sergey Chernov]

Just tried the 4.0.0-rc-3 comparing with 3.9.9, it's 4x times slower (!) on
a project of ~900 modules (700 of them are jar).
Maven 3 builds it in 2m57s, while Maven 4 in 11m48s (reproducible, with all
m2 caches). No build cache solutions enabled to compare pure build time.
Project is nothing special, just java 17 + kotlin 2.1 compilation (no test
execution).
It fits into the same heap memory. The CPU cores load is about the same
(but 4x longer).
It seems that somewhere there is a huge overhead.

Were there other performance tests at scale?


On Mon, May 26, 2025 at 4:48 PM Maarten Mulders 
wrote:

> Totally agree! I'm not trying to advocate "no more RC's", I'm trying to
> advocate "last RC should be as close as possible to the final product".
> And given what has happened between the last RC and today, I don't think
> we can cut 4.0.0 *today*. The diff is quite large IMO.
>
> Thanks,
>
>
> Maarten
>
> On May 26th, 2025 at 16:39, Elliotte Rusty Harold wrote:
> > On Mon, May 26, 2025 at 2:25 PM Maarten Mulders 
> wrote:
> >>
> >> That definition makes a lot of sense to me. If we would adhere to it, we
> >> should discipline ourselves after "a" next RC and *not* accept any code
> >> changes *except* for fixing critical uses.
> >
> > Be careful not to let the tail wag the dog. if changes are needed,
> > they're needed. You just need another RC. I would actually prefer that
> > RCs be identical to the release aside from version number, or even
> > better that the release candidate binary could simply become the
> > release, but that's not really how the Maven release process works.
> > However, critical bug fixes should generate a new RC. Overall I would
> > prefer much more rigorous versioning. Right now we're pushing RCs with
> > known unstable APIs, which I would normally consider appropriate for
> > pre-alpha builds.
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven 4.0.0 Release - Thoughts?

[Guillaume Nodet]

We cannot do that. We'd have to cut a new release and vote on it.
If the goal is to evaluate the release, we need to start voting a
4.0.0, open the vote, if any issue is considered blocking, cancel the
vote, fix the issue and cut another 4.0.0 release. If the issue is not
blocking, we can do a 4.0.1 a few days or weeks later.

Le lun. 26 mai 2025 à 14:14, Nikita Skvortsov
 a écrit :
>
> I believe having a "Release Candidate" is a good idea
>
> As long as it is indeed a candidate: a version that is exactly the same as
> a release, except for discovered critical issues and version numbers.
> I wonder if promoting a candidate to a GA without any code changes requires
> modification of existing community processes.
>
> ---
> Nikita Skvortsov
> Java Build Tools Team Lead
>
> JetBrains N.V. | KvK reg. nr. 56460279
> Gelrestraat 16, 1079 MZ Amsterdam, The Netherlands
> T: + 31 (0)20 205 01 18 | F: +31 (0)20 205 01 19
> E: nikita.skvort...@jetbrains.com
>
>
> On Sat, 24 May 2025 at 11:12, Romain Manni-Bucau 
> wrote:
>
> > Do we have the list of planned API changes?
> > Most changes can likely be limited using a "request/response object"
> > pattern (so we can add data without breaking instead of passing N
> > parameters), new methods dont break, so ultimately we are not worse than
> > 3.9.x in terms of stability if we respect that or do respect that in the
> > future.
> >
> > My point is that we can say the exact same reasons to never release v4
> > whereas it is adopted by several people since months now so we should let
> > it go and handle bugs as bugs and not as RC which doesnt mean anything
> > anymore IMHO.
> >
> > Romain Manni-Bucau
> > @rmannibucau  | .NET Blog
> >  | Blog 
> > | Old
> > Blog  | Github
> >  | LinkedIn
> >  | Book
> > <
> > https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064
> > >
> >
> >
> > Le ven. 23 mai 2025 à 19:32, Benjamin Marwell  a
> > écrit :
> >
> > > -1 for release, +1 for rc4.
> > > Reason: What Sylwester said, plus Nikita from JetBrains asking nicely.
> > > They (JB) would love to see API stability so they can ship an IntelliJ
> > > IDEA release in time with Maven 4.
> > > This of course applies to all other IDEs.
> > >
> > > Nikita is on #maven in slack, maybe also subscribed here? idk.
> > >
> > > Anyway, really strong reasons to do an RC4 first.
> > > This should not be hasted.
> > >
> > > - Ben
> > >
> > > Am Fr., 23. Mai 2025 um 00:05 Uhr schrieb Sylwester Lachiewicz
> > > :
> > > >
> > > > I would go for rc4 because we still have API changes after rc3 and our
> > > > plugins needs adjustments that could again require another, smaller
> > > > changes.
> > > > With current state of plugins 4.x they can't be used with latest
> > (master)
> > > > version so we could offer only 3.x for Maven 4.
> > > > Not so big issue for many users but without semi automatic way to move
> > > > plugin to new public API we are selling new "untested internally".
> > > >
> > > > In my opinion, if we could have releases of core plugins based on rc4
> > API
> > > > and our CI/CD pipelines runs also under Maven 4 - it would be safer.
> > > >
> > > > Sylwester
> > > >
> > > > śr., 21 maj 2025, 08:12 użytkownik Guillaume Nodet 
> > > > napisał:
> > > >
> > > > > Hey Maven Devs,
> > > > >
> > > > > We're gearing up to release a new version from the master branch. I'm
> > > > > thinking we should go for 4.0.0 instead of rc-4. What do you all
> > > think? Any
> > > > > feedback or ideas on the versioning or release plan? Let’s hear it!
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Guillaume
> > > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >



-- 

Guillaume Nodet

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

Re: Maven 4.0.0 Release - Thoughts?

[Guillaume Nodet]

Some plugins are known to cause important slow downs when executing in Maven 4.
This is the case for example of
https://github.com/tisonkun/os-detector which can be easily replaced
with https://github.com/maveniverse/nisse.
But I suppose there are other plugins that could cause the same behavior.

Le lun. 26 mai 2025 à 22:57, Sergey Chernov  a écrit :
>
> Just tried the 4.0.0-rc-3 comparing with 3.9.9, it's 4x times slower (!) on
> a project of ~900 modules (700 of them are jar).
> Maven 3 builds it in 2m57s, while Maven 4 in 11m48s (reproducible, with all
> m2 caches). No build cache solutions enabled to compare pure build time.
> Project is nothing special, just java 17 + kotlin 2.1 compilation (no test
> execution).
> It fits into the same heap memory. The CPU cores load is about the same
> (but 4x longer).
> It seems that somewhere there is a huge overhead.
>
> Were there other performance tests at scale?
>
>
> On Mon, May 26, 2025 at 4:48 PM Maarten Mulders 
> wrote:
>
> > Totally agree! I'm not trying to advocate "no more RC's", I'm trying to
> > advocate "last RC should be as close as possible to the final product".
> > And given what has happened between the last RC and today, I don't think
> > we can cut 4.0.0 *today*. The diff is quite large IMO.
> >
> > Thanks,
> >
> >
> > Maarten
> >
> > On May 26th, 2025 at 16:39, Elliotte Rusty Harold wrote:
> > > On Mon, May 26, 2025 at 2:25 PM Maarten Mulders 
> > wrote:
> > >>
> > >> That definition makes a lot of sense to me. If we would adhere to it, we
> > >> should discipline ourselves after "a" next RC and *not* accept any code
> > >> changes *except* for fixing critical uses.
> > >
> > > Be careful not to let the tail wag the dog. if changes are needed,
> > > they're needed. You just need another RC. I would actually prefer that
> > > RCs be identical to the release aside from version number, or even
> > > better that the release candidate binary could simply become the
> > > release, but that's not really how the Maven release process works.
> > > However, critical bug fixes should generate a new RC. Overall I would
> > > prefer much more rigorous versioning. Right now we're pushing RCs with
> > > known unstable APIs, which I would normally consider appropriate for
> > > pre-alpha builds.
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >



-- 

Guillaume Nodet

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

Re: [HEADS UP] Maven 3.9.10 release

[Sergey Chernov]

There is a problem using apache-maven-3.9.10-20250523.195106-41-bin.zip (
3.9.10-SNAPSHOT) version locally. When I run it with the existing mvnw wrapper
(which works quite well with apache-maven-3.9.9-bin.zip), there is a
failure mvnw.url: No such file or directory. The full log and the
configuration scripts you can find in the gist.

This may be related to using mode only-script in the
maven-wrapper.properties. This fails on both macOs and Linux.

Note: the wrapper works in case if maven-wrapper.jar is provided, but still

⚠️ The 3.9.10-SNAPSHOT looks like a breaking change ⚠️

There is a detailed log
https://gist.github.com/seregamorph/4c0cd5791cae7b7a52d884287ac3be45

P.S. I still believe that releasing a public release candidate for 3.9.10
is a good idea. E.g. for my enterprise setup it's a headache, because local
laptops cannot access internal artifactory (as it needs authentication) -
and the global URL is used in the committed in git wrapper properties.
While CI/CD is the opposite - it's restricted to access the internet and
the URL is replaced with local just before the build. In other words, I
cannot do a deep testing of this version (across hundreds of engineers!)
without revisiting our solution. You can say that's my problem (and you are
right), but if the purpose there is the better testing before release, it's
worth considering.

Also the public nexus for snapshots is relatively slow.

On Wed, May 21, 2025 at 6:06 PM Slawomir Jaranowski 
wrote:

> Hi
>
> Snapshot build is avaliable at:
>
>
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven/3.9.10-SNAPSHOT/
>
> look up for the latest build
>
>
> śr., 21 maj 2025, 17:39 użytkownik Sergey Chernov 
> napisał:
>
> > It would be great to have 3.9.10-rc-1 available at
> > https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/
> > similar to what is available for 4.0.0 versions. WDYT?
> > It’s much easier to use such dist instead of building own.
> >
> > > On 20 May 2025, at 22:00, Tamás Cservenák  wrote:
> > >
> > > I created one more issue and PR:
> > > https://github.com/apache/maven/pull/2361
> > >
> > > See related JIRA for context.
> > >
> > > Thanks
> > > T
> > >
> > > On Tue, May 20, 2025 at 9:24 PM Slawomir Jaranowski
> > >  wrote:
> > >>
> > >> Hi,
> > >>
> > >> I hope a list of issues for 3.9.10 is finished.
> > >>
> > >> Waiting for feedback, especially with JDK 24.
> > >>
> > >> I'm going to release it next week.
> > >>
> > >>
> > >> On Mon, 19 May 2025 at 20:46, Slawomir Jaranowski <
> > s.jaranow...@gmail.com>
> > >> wrote:
> > >>
> > >>>
> > >>>
> > >>> On Mon, 19 May 2025 at 20:42, Tamás Cservenák 
> > wrote:
> > >>>
> >  Sisu? Hopefully get released tomorrow.
> > 
> > >>>
> > >>> added to the list :-)
> > >>>
> > >>>
> > 
> >  T
> > 
> >  On Mon, May 19, 2025, 20:37 Slawomir Jaranowski <
> > s.jaranow...@gmail.com>
> >  wrote:
> > 
> > > Hi,
> > >
> > > We have resolved 32 issues
> > >
> > >
> > 
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.10
> > >
> > > The last one is in progress
> > > https://issues.apache.org/jira/browse/MNG-5913
> > >
> > > As we have many changes, I'm inviting you for testing a snapshot
> >  version,
> > > binary distribution can be downloaded from:
> > >
> > >
> > 
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven/3.9.10-SNAPSHOT/
> > > (please lookups for the latest build)
> > >
> > > or build from source code:
> > > https://github.com/apache/maven/tree/maven-3.9.x
> > >
> > >
> > > On Thu, 24 Apr 2025 at 23:30, Slawomir Jaranowski <
> >  s.jaranow...@gmail.com>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> I would like to release Maven 3.9.10
> > >>
> > >> We have planned issues:
> > >>
> > >>
> > >
> > 
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.10
> > >>
> > >> I also would like to release resolver 1.9.23
> > >> with issues:
> > >>
> > >>
> > >
> > 
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.23
> > >>
> > >> I will work on it, I hope the release can be done in the next two
> -
> >  three
> > >> weeks.
> > >> Any help as usual is appreciated.
> > >>
> > >>
> > >> --
> > >> Sławomir Jaranowski
> > >>
> > >
> > >
> > > --
> > > Sławomir Jaranowski
> > >
> > 
> > >>>
> > >>>
> > >>> --
> > >>> Sławomir Jaranowski
> > >>>
> > >>
> > >>
> > >> --
> > >> Sławomir Jaranowski
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> >
> >
>

Re: [HEADS UP] Maven 3.9.10 release

[James Gao]

I think we should not change the archive folder structure in a patch
release, and rollback to the previous name before GA.

On Mon, May 26, 2025 at 9:09 PM James Gao  wrote:

> @Sergey , the top folder name inside the zip file is different:
> 3.9.9: folder name is "apache-maven-3.9.9/"
> 3.9.10: folder name is "apache-maven/"
> so the script breaks since the folder pattern is changed.
>

Re: [HEADS UP] Maven 3.9.10 release

[Tamás Cservenák]

This is "CI build", which does NOT contain the version.
Reason for it is this:
https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
The `-PversionlessMavenDist`. By the way, master does not use this
anymore as it just creates a mixup like this one...

Thanks
T

On Mon, May 26, 2025 at 3:27 PM James Gao  wrote:
>
> I think we should not change the archive folder structure in a patch
> release, and rollback to the previous name before GA.
>
> On Mon, May 26, 2025 at 9:09 PM James Gao  wrote:
>
> > @Sergey , the top folder name inside the zip file is different:
> > 3.9.9: folder name is "apache-maven-3.9.9/"
> > 3.9.10: folder name is "apache-maven/"
> > so the script breaks since the folder pattern is changed.
> >

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

Re: Maven 4.0.0 Release - Thoughts?

[Maarten Mulders]

Totally agree! I'm not trying to advocate "no more RC's", I'm trying to 
advocate "last RC should be as close as possible to the final product". 
And given what has happened between the last RC and today, I don't think 
we can cut 4.0.0 *today*. The diff is quite large IMO.


Thanks,


Maarten

On May 26th, 2025 at 16:39, Elliotte Rusty Harold wrote:

On Mon, May 26, 2025 at 2:25 PM Maarten Mulders  wrote:


That definition makes a lot of sense to me. If we would adhere to it, we
should discipline ourselves after "a" next RC and *not* accept any code
changes *except* for fixing critical uses.


Be careful not to let the tail wag the dog. if changes are needed,
they're needed. You just need another RC. I would actually prefer that
RCs be identical to the release aside from version number, or even
better that the release candidate binary could simply become the
release, but that's not really how the Maven release process works.
However, critical bug fixes should generate a new RC. Overall I would
prefer much more rigorous versioning. Right now we're pushing RCs with
known unstable APIs, which I would normally consider appropriate for
pre-alpha builds.




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

Re: [HEADS UP] Maven 3.9.10 release

[Slawomir Jaranowski]

Hi,

For easy testing I have published latest version at:

https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.10-SNAPSHOT/

The same distribution will be done during releases.


On Mon, 26 May 2025 at 15:45, Tamás Cservenák  wrote:

> This is "CI build", which does NOT contain the version.
> Reason for it is this:
> https://github.com/apache/maven/blob/maven-3.9.x/Jenkinsfile#L56
> The `-PversionlessMavenDist`. By the way, master does not use this
> anymore as it just creates a mixup like this one...
>
> Thanks
> T
>
> On Mon, May 26, 2025 at 3:27 PM James Gao  wrote:
> >
> > I think we should not change the archive folder structure in a patch
> > release, and rollback to the previous name before GA.
> >
> > On Mon, May 26, 2025 at 9:09 PM James Gao  wrote:
> >
> > > @Sergey , the top folder name inside the zip file is different:
> > > 3.9.9: folder name is "apache-maven-3.9.9/"
> > > 3.9.10: folder name is "apache-maven/"
> > > so the script breaks since the folder pattern is changed.
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Sławomir Jaranowski

Re: Maven 4.0.0 Release - Thoughts?

[Maarten Mulders]

That definition makes a lot of sense to me. If we would adhere to it, we 
should discipline ourselves after "a" next RC and *not* accept any code 
changes *except* for fixing critical uses.


I think there have been too many changes since last RC to cut a 4.0.0 today.


Maarten

On 26/05/2025 14:14, Nikita Skvortsov wrote:

I believe having a "Release Candidate" is a good idea

As long as it is indeed a candidate: a version that is exactly the same as
a release, except for discovered critical issues and version numbers.
I wonder if promoting a candidate to a GA without any code changes requires
modification of existing community processes.

---
Nikita Skvortsov
Java Build Tools Team Lead

JetBrains N.V. | KvK reg. nr. 56460279
Gelrestraat 16, 1079 MZ Amsterdam, The Netherlands
T: + 31 (0)20 205 01 18 | F: +31 (0)20 205 01 19
E: nikita.skvort...@jetbrains.com


On Sat, 24 May 2025 at 11:12, Romain Manni-Bucau 
wrote:


Do we have the list of planned API changes?
Most changes can likely be limited using a "request/response object"
pattern (so we can add data without breaking instead of passing N
parameters), new methods dont break, so ultimately we are not worse than
3.9.x in terms of stability if we respect that or do respect that in the
future.

My point is that we can say the exact same reasons to never release v4
whereas it is adopted by several people since months now so we should let
it go and handle bugs as bugs and not as RC which doesnt mean anything
anymore IMHO.

Romain Manni-Bucau
@rmannibucau  | .NET Blog
 | Blog 
| Old
Blog  | Github
 | LinkedIn
 | Book
<
https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064





Le ven. 23 mai 2025 à 19:32, Benjamin Marwell  a
écrit :


-1 for release, +1 for rc4.
Reason: What Sylwester said, plus Nikita from JetBrains asking nicely.
They (JB) would love to see API stability so they can ship an IntelliJ
IDEA release in time with Maven 4.
This of course applies to all other IDEs.

Nikita is on #maven in slack, maybe also subscribed here? idk.

Anyway, really strong reasons to do an RC4 first.
This should not be hasted.

- Ben

Am Fr., 23. Mai 2025 um 00:05 Uhr schrieb Sylwester Lachiewicz
:


I would go for rc4 because we still have API changes after rc3 and our
plugins needs adjustments that could again require another, smaller
changes.
With current state of plugins 4.x they can't be used with latest

(master)

version so we could offer only 3.x for Maven 4.
Not so big issue for many users but without semi automatic way to move
plugin to new public API we are selling new "untested internally".

In my opinion, if we could have releases of core plugins based on rc4

API

and our CI/CD pipelines runs also under Maven 4 - it would be safer.

Sylwester

śr., 21 maj 2025, 08:12 użytkownik Guillaume Nodet 
napisał:


Hey Maven Devs,

We're gearing up to release a new version from the master branch. I'm
thinking we should go for 4.0.0 instead of rc-4. What do you all

think? Any

feedback or ideas on the versioning or release plan? Let’s hear it!

Cheers,

Guillaume



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









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

Re: Maven 4.0.0 Release - Thoughts?

[Elliotte Rusty Harold]

On Mon, May 26, 2025 at 2:25 PM Maarten Mulders  wrote:
>
> That definition makes a lot of sense to me. If we would adhere to it, we
> should discipline ourselves after "a" next RC and *not* accept any code
> changes *except* for fixing critical uses.

Be careful not to let the tail wag the dog. if changes are needed,
they're needed. You just need another RC. I would actually prefer that
RCs be identical to the release aside from version number, or even
better that the release candidate binary could simply become the
release, but that's not really how the Maven release process works.
However, critical bug fixes should generate a new RC. Overall I would
prefer much more rigorous versioning. Right now we're pushing RCs with
known unstable APIs, which I would normally consider appropriate for
pre-alpha builds.

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

Re: Maven 4.0.0 Release - Thoughts?

[Nikita Skvortsov]

I believe having a "Release Candidate" is a good idea

As long as it is indeed a candidate: a version that is exactly the same as
a release, except for discovered critical issues and version numbers.
I wonder if promoting a candidate to a GA without any code changes requires
modification of existing community processes.

---
Nikita Skvortsov
Java Build Tools Team Lead

JetBrains N.V. | KvK reg. nr. 56460279
Gelrestraat 16, 1079 MZ Amsterdam, The Netherlands
T: + 31 (0)20 205 01 18 | F: +31 (0)20 205 01 19
E: nikita.skvort...@jetbrains.com


On Sat, 24 May 2025 at 11:12, Romain Manni-Bucau 
wrote:

> Do we have the list of planned API changes?
> Most changes can likely be limited using a "request/response object"
> pattern (so we can add data without breaking instead of passing N
> parameters), new methods dont break, so ultimately we are not worse than
> 3.9.x in terms of stability if we respect that or do respect that in the
> future.
>
> My point is that we can say the exact same reasons to never release v4
> whereas it is adopted by several people since months now so we should let
> it go and handle bugs as bugs and not as RC which doesnt mean anything
> anymore IMHO.
>
> Romain Manni-Bucau
> @rmannibucau  | .NET Blog
>  | Blog 
> | Old
> Blog  | Github
>  | LinkedIn
>  | Book
> <
> https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064
> >
>
>
> Le ven. 23 mai 2025 à 19:32, Benjamin Marwell  a
> écrit :
>
> > -1 for release, +1 for rc4.
> > Reason: What Sylwester said, plus Nikita from JetBrains asking nicely.
> > They (JB) would love to see API stability so they can ship an IntelliJ
> > IDEA release in time with Maven 4.
> > This of course applies to all other IDEs.
> >
> > Nikita is on #maven in slack, maybe also subscribed here? idk.
> >
> > Anyway, really strong reasons to do an RC4 first.
> > This should not be hasted.
> >
> > - Ben
> >
> > Am Fr., 23. Mai 2025 um 00:05 Uhr schrieb Sylwester Lachiewicz
> > :
> > >
> > > I would go for rc4 because we still have API changes after rc3 and our
> > > plugins needs adjustments that could again require another, smaller
> > > changes.
> > > With current state of plugins 4.x they can't be used with latest
> (master)
> > > version so we could offer only 3.x for Maven 4.
> > > Not so big issue for many users but without semi automatic way to move
> > > plugin to new public API we are selling new "untested internally".
> > >
> > > In my opinion, if we could have releases of core plugins based on rc4
> API
> > > and our CI/CD pipelines runs also under Maven 4 - it would be safer.
> > >
> > > Sylwester
> > >
> > > śr., 21 maj 2025, 08:12 użytkownik Guillaume Nodet 
> > > napisał:
> > >
> > > > Hey Maven Devs,
> > > >
> > > > We're gearing up to release a new version from the master branch. I'm
> > > > thinking we should go for 4.0.0 instead of rc-4. What do you all
> > think? Any
> > > > feedback or ideas on the versioning or release plan? Let’s hear it!
> > > >
> > > > Cheers,
> > > >
> > > > Guillaume
> > > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: [HEADS UP] Maven 3.9.10 release

[James Gao]

@Sergey , the top folder name inside the zip file is different:
3.9.9: folder name is "apache-maven-3.9.9/"
3.9.10: folder name is "apache-maven/"
so the script breaks since the folder pattern is changed.

On Mon, May 26, 2025 at 7:54 PM Sergey Chernov 
wrote:

> There is a problem using apache-maven-3.9.10-20250523.195106-41-bin.zip (
> 3.9.10-SNAPSHOT) version locally. When I run it with the existing mvnw
> wrapper
> (which works quite well with apache-maven-3.9.9-bin.zip), there is a
> failure mvnw.url: No such file or directory. The full log and the
> configuration scripts you can find in the gist.
>
> This may be related to using mode only-script in the
> maven-wrapper.properties. This fails on both macOs and Linux.
>
> Note: the wrapper works in case if maven-wrapper.jar is provided, but still
>
> ⚠️ The 3.9.10-SNAPSHOT looks like a breaking change ⚠️
>
> There is a detailed log
> https://gist.github.com/seregamorph/4c0cd5791cae7b7a52d884287ac3be45
>
> P.S. I still believe that releasing a public release candidate for 3.9.10
> is a good idea. E.g. for my enterprise setup it's a headache, because local
> laptops cannot access internal artifactory (as it needs authentication) -
> and the global URL is used in the committed in git wrapper properties.
> While CI/CD is the opposite - it's restricted to access the internet and
> the URL is replaced with local just before the build. In other words, I
> cannot do a deep testing of this version (across hundreds of engineers!)
> without revisiting our solution. You can say that's my problem (and you are
> right), but if the purpose there is the better testing before release, it's
> worth considering.
>
> Also the public nexus for snapshots is relatively slow.
>
> On Wed, May 21, 2025 at 6:06 PM Slawomir Jaranowski <
> s.jaranow...@gmail.com>
> wrote:
>
> > Hi
> >
> > Snapshot build is avaliable at:
> >
> >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven/3.9.10-SNAPSHOT/
> >
> > look up for the latest build
> >
> >
> > śr., 21 maj 2025, 17:39 użytkownik Sergey Chernov <
> serega.mo...@gmail.com>
> > napisał:
> >
> > > It would be great to have 3.9.10-rc-1 available at
> > > https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/
> > > similar to what is available for 4.0.0 versions. WDYT?
> > > It’s much easier to use such dist instead of building own.
> > >
> > > > On 20 May 2025, at 22:00, Tamás Cservenák 
> wrote:
> > > >
> > > > I created one more issue and PR:
> > > > https://github.com/apache/maven/pull/2361
> > > >
> > > > See related JIRA for context.
> > > >
> > > > Thanks
> > > > T
> > > >
> > > > On Tue, May 20, 2025 at 9:24 PM Slawomir Jaranowski
> > > >  wrote:
> > > >>
> > > >> Hi,
> > > >>
> > > >> I hope a list of issues for 3.9.10 is finished.
> > > >>
> > > >> Waiting for feedback, especially with JDK 24.
> > > >>
> > > >> I'm going to release it next week.
> > > >>
> > > >>
> > > >> On Mon, 19 May 2025 at 20:46, Slawomir Jaranowski <
> > > s.jaranow...@gmail.com>
> > > >> wrote:
> > > >>
> > > >>>
> > > >>>
> > > >>> On Mon, 19 May 2025 at 20:42, Tamás Cservenák  >
> > > wrote:
> > > >>>
> > >  Sisu? Hopefully get released tomorrow.
> > > 
> > > >>>
> > > >>> added to the list :-)
> > > >>>
> > > >>>
> > > 
> > >  T
> > > 
> > >  On Mon, May 19, 2025, 20:37 Slawomir Jaranowski <
> > > s.jaranow...@gmail.com>
> > >  wrote:
> > > 
> > > > Hi,
> > > >
> > > > We have resolved 32 issues
> > > >
> > > >
> > > 
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.10
> > > >
> > > > The last one is in progress
> > > > https://issues.apache.org/jira/browse/MNG-5913
> > > >
> > > > As we have many changes, I'm inviting you for testing a snapshot
> > >  version,
> > > > binary distribution can be downloaded from:
> > > >
> > > >
> > > 
> > >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/apache-maven/3.9.10-SNAPSHOT/
> > > > (please lookups for the latest build)
> > > >
> > > > or build from source code:
> > > > https://github.com/apache/maven/tree/maven-3.9.x
> > > >
> > > >
> > > > On Thu, 24 Apr 2025 at 23:30, Slawomir Jaranowski <
> > >  s.jaranow...@gmail.com>
> > > > wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> I would like to release Maven 3.9.10
> > > >>
> > > >> We have planned issues:
> > > >>
> > > >>
> > > >
> > > 
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.10
> > > >>
> > > >> I also would like to release resolver 1.9.23
> > > >> with issues:
> > > >>
> > > >>
> > > >
> > > 
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.23
> > > >>
> > > >> I will work on it, I hope the r