`JFrogMaven@1` fails with latest Azure Pipelines agents because of upgrade to Maven 3.9.12

[Slooz]

Describe the bug

JFrogMaven@1 is incompatible with Maven 3.9.12. See jfrog/jfrog-cli#3285.

Here is a workaround by downgrading Maven to 3.9.11:

bash: |
  set -o errexit
  set -o nounset
  set -o pipefail
  curl --fail --location --show-error \
      --silent https://archive.apache.org/dist/maven/maven-3/3.9.11/binaries/apache-maven-3.9.11-bin.tar.gz |
      tar --extract --gzip --directory=/opt
  echo "##vso[task.prependpath]/opt/apache-maven-3.9.11/bin"
displayName: Downgrade Maven to 3.9.11

Current behavior

JFrogMaven@1 fails with latest Azure Pipelines agent. See the following error:

[main] ERROR org.apache.maven.cli.MavenCli - Cannot invoke "java.util.List.forEach(java.util.function.Consumer)" because "this.prerequisitesCheckers" is null

Reproduction steps

No response

Expected behavior

No response

Azure DevOps extension name and version

New JFrog Azure Devops Extension 2.12.4

JFrog CLI version

2.85.0

Operating system type and version

Ubuntu 24.04.3 LTS, Agent Version: 4.266.2, Runner Image Version: 20260105.202.1

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

JFrog Distribution version (if relevant)

No response

[munzli]

another workaround is to use a symbolic link to force the extension to use the maven wrapper.

      - task: Bash@3
        displayName: 'Force mvn wrapper'
        inputs:
          targetType: 'inline'
          script: |
            mkdir $(Build.SourcesDirectory)/.mvn/bin
            ln -sf $(Build.SourcesDirectory)/mvnw $(Build.SourcesDirectory)/.mvn/bin/mvn
            echo "##vso[task.prependpath]$(Build.SourcesDirectory)/.mvn/bin"