trasloco

Maven@1 is retired: replace it with Maven@4

The short answer

Retirement date
Removal date
. Pipelines that still use it fail after removal.
Replacement
Maven@4
Kind of migration
replacement with input changes
Automatic rewrite
Not yet. Automatic rewrite is planned for this kind of task (replacement with input changes). Today, trasloco modernize --check finds the step and you change it by hand.
Recommended action
Replace Maven@1 with Maven@4 and review the replacement inputs before updating the pipeline.

Official sources

Last verified:

Why does my pipeline show a retirement error for Maven@1?

On , Azure Pipelines shows a retirement error for Maven@1, but the run does not fail. On , pipelines that still use Maven@1 fail.

Find it in your pipelines

With trasloco:

trasloco modernize --check

Install trasloco from the latest release.

With plain grep, nothing to install:

grep -rniwF 'Maven@1' --include='*.yml' --include='*.yaml' .

How to migrate

Replace Maven@1 with Maven@4 and review the replacement inputs before updating the pipeline.

The task definition of the replacement is linked under official sources above.

Maven@1 retirement FAQ

Is Maven@1 deprecated?

Yes. Maven@1 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.

When does Maven@1 stop working?

Maven@1 is removed on 2027-03-15. Pipelines that still use it fail after removal.

What should I use instead of Maven@1?

Replace Maven@1 with Maven@4.