You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Sylwester Lachiewicz <sl...@apache.org> on 2026/09/21 13:34:33 UTC
[VOTE] Retire Maven Verifier
Hi,
Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
favor of Maven Executor (org.apache.maven.executor:maven-executor),
released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
embedded mode without the CLI-specific helper code that Verifier had to
carry.
The repository is not totally abandoned: it received a migration guide, an
@Deprecated marking of the API, and, this week, a fix that lets the
embedded launcher start Maven 4 [2]. However, it no longer has a reason to
exist: every Maven project that used it (the core integration tests on the
3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
Remote Resources plugins, and the Apache resources bundles) has moved to
Maven Executor.
I therefore propose that we retire maven-verifier.
If this vote is successful, I will make one final release (2.0.0) that
carries the Maven 4 embedded-launcher fix, the migration guide, and a
"(RETIRED)" marker in the project name and on the site. This will ensure
anyone who still resolves the artifact learns of the retirement directly
from it. After that, the source code repository will be archived
(read-only).
Projects outside Maven that still declare the dependency
(tomcat-maven-plugin, brooklyn-library,
jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
geronimo-genesis, npanday-its) will continue to work on that final release,
and the migration guide [4] describes the move for them.
The process for retiring a component is described here:
https://maven.apache.org/developers/retirement-plan-plugins.html
The vote is open for 72 hours:
[ ] +1 Yes, it's about time
[ ] -1 No, because...
Thanks,
Sylwester
[1] https://github.com/apache/maven-verifier/issues/186
[2] https://github.com/apache/maven-verifier/issues/215
[3] https://github.com/apache/maven-executor/issues/49
[4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
Re: [VOTE] Retire Maven Verifier
Posted by Sylwester Lachiewicz <sl...@gmail.com>.
Hi,
Friendly reminder: the vote to retire Maven Verifier is still open and has
not reached quorum yet.
So far we have one binding +1 (thanks, Elliotte). We need at least three
binding +1 votes to pass.
Maven Verifier has been deprecated since August 2025 in favour of Maven
Executor, and its last release was 2.0.0-M1 in 2022. Details are in the
original mail below.
PMC members, please cast your vote when you have a moment. I'll keep the
vote open for a few more days and close it once quorum is reached.
[ ] +1 Retire Maven Verifier
[ ] +0
[ ] -1 (please give a reason)
Thanks,
Sylwester
On Tue, Sep 22, 2026 01:30 PM, Elliotte Rusty Harold <el...@ibiblio.org>
wrote:
> +1
>
> On Mon, Sep 21, 2026 at 9:35 AM Sylwester Lachiewicz
> <sl...@apache.org> wrote:
> >
> > Hi,
> >
> > Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
> > as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
> > favor of Maven Executor (org.apache.maven.executor:maven-executor),
> > released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
> > embedded mode without the CLI-specific helper code that Verifier had to
> > carry.
> >
> > The repository is not totally abandoned: it received a migration guide,
> an
> > @Deprecated marking of the API, and, this week, a fix that lets the
> > embedded launcher start Maven 4 [2]. However, it no longer has a reason
> to
> > exist: every Maven project that used it (the core integration tests on
> the
> > 3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
> > Remote Resources plugins, and the Apache resources bundles) has moved to
> > Maven Executor.
> >
> > I therefore propose that we retire maven-verifier.
> >
> > If this vote is successful, I will make one final release (2.0.0) that
> > carries the Maven 4 embedded-launcher fix, the migration guide, and a
> > "(RETIRED)" marker in the project name and on the site. This will ensure
> > anyone who still resolves the artifact learns of the retirement directly
> > from it. After that, the source code repository will be archived
> > (read-only).
> >
> > Projects outside Maven that still declare the dependency
> > (tomcat-maven-plugin, brooklyn-library,
> > jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
> > geronimo-genesis, npanday-its) will continue to work on that final
> release,
> > and the migration guide [4] describes the move for them.
> >
> > The process for retiring a component is described here:
> > https://maven.apache.org/developers/retirement-plan-plugins.html
> >
> > The vote is open for 72 hours:
> >
> > [ ] +1 Yes, it's about time
> > [ ] -1 No, because...
> >
> > Thanks,
> > Sylwester
> >
> > [1] https://github.com/apache/maven-verifier/issues/186
> > [2] https://github.com/apache/maven-verifier/issues/215
> > [3] https://github.com/apache/maven-executor/issues/49
> > [4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
>
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] Retire Maven Verifier
Posted by Sylwester Lachiewicz <sl...@gmail.com>.
Hi,
Friendly reminder: the vote to retire Maven Verifier is still open and has
not reached quorum yet.
So far we have one binding +1 (thanks, Elliotte). We need at least three
binding +1 votes to pass.
Maven Verifier has been deprecated since August 2025 in favour of Maven
Executor, and its last release was 2.0.0-M1 in 2022. Details are in the
original mail below.
PMC members, please cast your vote when you have a moment. I'll keep the
vote open for a few more days and close it once quorum is reached.
[ ] +1 Retire Maven Verifier
[ ] +0
[ ] -1 (please give a reason)
Thanks,
Sylwester
On Tue, Sep 22, 2026 01:30 PM, Elliotte Rusty Harold <el...@ibiblio.org>
wrote:
> +1
>
> On Mon, Sep 21, 2026 at 9:35 AM Sylwester Lachiewicz
> <sl...@apache.org> wrote:
> >
> > Hi,
> >
> > Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
> > as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
> > favor of Maven Executor (org.apache.maven.executor:maven-executor),
> > released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
> > embedded mode without the CLI-specific helper code that Verifier had to
> > carry.
> >
> > The repository is not totally abandoned: it received a migration guide,
> an
> > @Deprecated marking of the API, and, this week, a fix that lets the
> > embedded launcher start Maven 4 [2]. However, it no longer has a reason
> to
> > exist: every Maven project that used it (the core integration tests on
> the
> > 3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
> > Remote Resources plugins, and the Apache resources bundles) has moved to
> > Maven Executor.
> >
> > I therefore propose that we retire maven-verifier.
> >
> > If this vote is successful, I will make one final release (2.0.0) that
> > carries the Maven 4 embedded-launcher fix, the migration guide, and a
> > "(RETIRED)" marker in the project name and on the site. This will ensure
> > anyone who still resolves the artifact learns of the retirement directly
> > from it. After that, the source code repository will be archived
> > (read-only).
> >
> > Projects outside Maven that still declare the dependency
> > (tomcat-maven-plugin, brooklyn-library,
> > jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
> > geronimo-genesis, npanday-its) will continue to work on that final
> release,
> > and the migration guide [4] describes the move for them.
> >
> > The process for retiring a component is described here:
> > https://maven.apache.org/developers/retirement-plan-plugins.html
> >
> > The vote is open for 72 hours:
> >
> > [ ] +1 Yes, it's about time
> > [ ] -1 No, because...
> >
> > Thanks,
> > Sylwester
> >
> > [1] https://github.com/apache/maven-verifier/issues/186
> > [2] https://github.com/apache/maven-verifier/issues/215
> > [3] https://github.com/apache/maven-executor/issues/49
> > [4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
>
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] Retire Maven Verifier
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
+1
On Mon, Sep 21, 2026 at 9:35 AM Sylwester Lachiewicz
<sl...@apache.org> wrote:
>
> Hi,
>
> Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
> as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
> favor of Maven Executor (org.apache.maven.executor:maven-executor),
> released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
> embedded mode without the CLI-specific helper code that Verifier had to
> carry.
>
> The repository is not totally abandoned: it received a migration guide, an
> @Deprecated marking of the API, and, this week, a fix that lets the
> embedded launcher start Maven 4 [2]. However, it no longer has a reason to
> exist: every Maven project that used it (the core integration tests on the
> 3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
> Remote Resources plugins, and the Apache resources bundles) has moved to
> Maven Executor.
>
> I therefore propose that we retire maven-verifier.
>
> If this vote is successful, I will make one final release (2.0.0) that
> carries the Maven 4 embedded-launcher fix, the migration guide, and a
> "(RETIRED)" marker in the project name and on the site. This will ensure
> anyone who still resolves the artifact learns of the retirement directly
> from it. After that, the source code repository will be archived
> (read-only).
>
> Projects outside Maven that still declare the dependency
> (tomcat-maven-plugin, brooklyn-library,
> jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
> geronimo-genesis, npanday-its) will continue to work on that final release,
> and the migration guide [4] describes the move for them.
>
> The process for retiring a component is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html
>
> The vote is open for 72 hours:
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> Thanks,
> Sylwester
>
> [1] https://github.com/apache/maven-verifier/issues/186
> [2] https://github.com/apache/maven-verifier/issues/215
> [3] https://github.com/apache/maven-executor/issues/49
> [4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Retire Maven Verifier
Posted by Slawomir Jaranowski <s....@gmail.com>.
+1
Sławomir Jaranowski
pon., 21 wrz 2026, 15:34 użytkownik Sylwester Lachiewicz <
slachiewicz@apache.org> napisał:
> Hi,
>
> Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
> as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
> favor of Maven Executor (org.apache.maven.executor:maven-executor),
> released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
> embedded mode without the CLI-specific helper code that Verifier had to
> carry.
>
> The repository is not totally abandoned: it received a migration guide, an
> @Deprecated marking of the API, and, this week, a fix that lets the
> embedded launcher start Maven 4 [2]. However, it no longer has a reason to
> exist: every Maven project that used it (the core integration tests on the
> 3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
> Remote Resources plugins, and the Apache resources bundles) has moved to
> Maven Executor.
>
> I therefore propose that we retire maven-verifier.
>
> If this vote is successful, I will make one final release (2.0.0) that
> carries the Maven 4 embedded-launcher fix, the migration guide, and a
> "(RETIRED)" marker in the project name and on the site. This will ensure
> anyone who still resolves the artifact learns of the retirement directly
> from it. After that, the source code repository will be archived
> (read-only).
>
> Projects outside Maven that still declare the dependency
> (tomcat-maven-plugin, brooklyn-library,
> jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
> geronimo-genesis, npanday-its) will continue to work on that final release,
> and the migration guide [4] describes the move for them.
>
> The process for retiring a component is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html
>
> The vote is open for 72 hours:
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> Thanks,
> Sylwester
>
> [1] https://github.com/apache/maven-verifier/issues/186
> [2] https://github.com/apache/maven-verifier/issues/215
> [3] https://github.com/apache/maven-executor/issues/49
> [4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
>
Re: [VOTE] Retire Maven Verifier
Posted by Karl Heinz Marbaise via users <us...@maven.apache.org>.
Hi,
+1 from me,
Kind regards
Karl Heinz Marbaise
On 21.09.26 15:34, Sylwester Lachiewicz wrote:
> Hi,
>
> Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
> as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
> favor of Maven Executor (org.apache.maven.executor:maven-executor),
> released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
> embedded mode without the CLI-specific helper code that Verifier had to
> carry.
>
> The repository is not totally abandoned: it received a migration guide, an
> @Deprecated marking of the API, and, this week, a fix that lets the
> embedded launcher start Maven 4 [2]. However, it no longer has a reason to
> exist: every Maven project that used it (the core integration tests on the
> 3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
> Remote Resources plugins, and the Apache resources bundles) has moved to
> Maven Executor.
>
> I therefore propose that we retire maven-verifier.
>
> If this vote is successful, I will make one final release (2.0.0) that
> carries the Maven 4 embedded-launcher fix, the migration guide, and a
> "(RETIRED)" marker in the project name and on the site. This will ensure
> anyone who still resolves the artifact learns of the retirement directly
> from it. After that, the source code repository will be archived
> (read-only).
>
> Projects outside Maven that still declare the dependency
> (tomcat-maven-plugin, brooklyn-library,
> jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
> geronimo-genesis, npanday-its) will continue to work on that final release,
> and the migration guide [4] describes the move for them.
>
> The process for retiring a component is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html
>
> The vote is open for 72 hours:
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> Thanks,
> Sylwester
>
> [1] https://github.com/apache/maven-verifier/issues/186
> [2] https://github.com/apache/maven-verifier/issues/215
> [3] https://github.com/apache/maven-executor/issues/49
> [4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [VOTE] Retire Maven Verifier
Posted by Tamás Cservenák <ta...@cservenak.net>.
+1
On Mon, Sep 21, 2026, 15:34 Sylwester Lachiewicz <sl...@apache.org>
wrote:
> Hi,
>
> Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
> as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
> favor of Maven Executor (org.apache.maven.executor:maven-executor),
> released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
> embedded mode without the CLI-specific helper code that Verifier had to
> carry.
>
> The repository is not totally abandoned: it received a migration guide, an
> @Deprecated marking of the API, and, this week, a fix that lets the
> embedded launcher start Maven 4 [2]. However, it no longer has a reason to
> exist: every Maven project that used it (the core integration tests on the
> 3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
> Remote Resources plugins, and the Apache resources bundles) has moved to
> Maven Executor.
>
> I therefore propose that we retire maven-verifier.
>
> If this vote is successful, I will make one final release (2.0.0) that
> carries the Maven 4 embedded-launcher fix, the migration guide, and a
> "(RETIRED)" marker in the project name and on the site. This will ensure
> anyone who still resolves the artifact learns of the retirement directly
> from it. After that, the source code repository will be archived
> (read-only).
>
> Projects outside Maven that still declare the dependency
> (tomcat-maven-plugin, brooklyn-library,
> jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
> geronimo-genesis, npanday-its) will continue to work on that final release,
> and the migration guide [4] describes the move for them.
>
> The process for retiring a component is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html
>
> The vote is open for 72 hours:
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> Thanks,
> Sylwester
>
> [1] https://github.com/apache/maven-verifier/issues/186
> [2] https://github.com/apache/maven-verifier/issues/215
> [3] https://github.com/apache/maven-executor/issues/49
> [4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
>
Re: [VOTE] Retire Maven Verifier
Posted by Karl Heinz Marbaise via dev <de...@maven.apache.org>.
Hi,
+1 from me,
Kind regards
Karl Heinz Marbaise
On 21.09.26 15:34, Sylwester Lachiewicz wrote:
> Hi,
>
> Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
> as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
> favor of Maven Executor (org.apache.maven.executor:maven-executor),
> released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
> embedded mode without the CLI-specific helper code that Verifier had to
> carry.
>
> The repository is not totally abandoned: it received a migration guide, an
> @Deprecated marking of the API, and, this week, a fix that lets the
> embedded launcher start Maven 4 [2]. However, it no longer has a reason to
> exist: every Maven project that used it (the core integration tests on the
> 3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
> Remote Resources plugins, and the Apache resources bundles) has moved to
> Maven Executor.
>
> I therefore propose that we retire maven-verifier.
>
> If this vote is successful, I will make one final release (2.0.0) that
> carries the Maven 4 embedded-launcher fix, the migration guide, and a
> "(RETIRED)" marker in the project name and on the site. This will ensure
> anyone who still resolves the artifact learns of the retirement directly
> from it. After that, the source code repository will be archived
> (read-only).
>
> Projects outside Maven that still declare the dependency
> (tomcat-maven-plugin, brooklyn-library,
> jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
> geronimo-genesis, npanday-its) will continue to work on that final release,
> and the migration guide [4] describes the move for them.
>
> The process for retiring a component is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html
>
> The vote is open for 72 hours:
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> Thanks,
> Sylwester
>
> [1] https://github.com/apache/maven-verifier/issues/186
> [2] https://github.com/apache/maven-verifier/issues/215
> [3] https://github.com/apache/maven-executor/issues/49
> [4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Retire Maven Verifier
Posted by Slawomir Jaranowski <s....@gmail.com>.
+1
Sławomir Jaranowski
pon., 21 wrz 2026, 15:34 użytkownik Sylwester Lachiewicz <
slachiewicz@apache.org> napisał:
> Hi,
>
> Maven Verifier (org.apache.maven.shared:maven-verifier) was last released
> as 2.0.0-M1 on 2022-09-22. It has been deprecated since August 2025 in
> favor of Maven Executor (org.apache.maven.executor:maven-executor),
> released as 1.0.0 on 2026-06-15, which runs Maven 3.9 and 4 in forked or
> embedded mode without the CLI-specific helper code that Verifier had to
> carry.
>
> The repository is not totally abandoned: it received a migration guide, an
> @Deprecated marking of the API, and, this week, a fix that lets the
> embedded launcher start Maven 4 [2]. However, it no longer has a reason to
> exist: every Maven project that used it (the core integration tests on the
> 3.9.x and 3.10.x lines, Surefire, the Build Cache extension, the EAR and
> Remote Resources plugins, and the Apache resources bundles) has moved to
> Maven Executor.
>
> I therefore propose that we retire maven-verifier.
>
> If this vote is successful, I will make one final release (2.0.0) that
> carries the Maven 4 embedded-launcher fix, the migration guide, and a
> "(RETIRED)" marker in the project name and on the site. This will ensure
> anyone who still resolves the artifact learns of the retirement directly
> from it. After that, the source code repository will be archived
> (read-only).
>
> Projects outside Maven that still declare the dependency
> (tomcat-maven-plugin, brooklyn-library,
> jackrabbit-filevault-package-maven-plugin, manifoldcf-sdk,
> geronimo-genesis, npanday-its) will continue to work on that final release,
> and the migration guide [4] describes the move for them.
>
> The process for retiring a component is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html
>
> The vote is open for 72 hours:
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> Thanks,
> Sylwester
>
> [1] https://github.com/apache/maven-verifier/issues/186
> [2] https://github.com/apache/maven-verifier/issues/215
> [3] https://github.com/apache/maven-executor/issues/49
> [4] https://github.com/apache/maven-verifier/blob/master/MIGRATION.md
>