Skip to content

devops: resolve exec plugin prefix without group metadata - #1987

Merged
Yury Semikhatsky (yury-s) merged 1 commit into
microsoft:mainfrom
yury-s:docker-exec-plugin-prefix
Sep 15, 2026
Merged

Yury Semikhatsky (yury-s) merged 1 commit into
microsoft:mainfrom
yury-s:docker-exec-plugin-prefix

Conversation

@yury-s

@yury-s Yury Semikhatsky (yury-s) commented Sep 15, 2026

Copy link
Copy Markdown
Member

Summary

  • Declare exec-maven-plugin in pluginManagement so the exec: prefix resolves from the POM; the DevDiv_PublicPackages feed returns 404 for org/codehaus/mojo/maven-metadata.xml, which broke publish_docker.sh and the Dockerfiles' mvn exec:java.
  • Print Maven output when publish_docker.sh fails to read the project version instead of exiting silently.

The pipeline step failed with no output:

MAVEN_SETTINGS_SECRET="$HOME/.m2/settings.xml" ./utils/docker/publish_docker.sh canary
##[error]Bash exited with code '1'.

The swallowed Maven error:

[ERROR] No plugin found for prefix 'exec' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (~/.m2/repository), DevDiv_PublicPackages (https://pkgs.dev.azure.com/devdiv/DevDiv/_packaging/DevDiv_PublicPackages/maven/v1)] -> [Help 1]

The DevDiv_PublicPackages feed does not serve org/codehaus/mojo/maven-metadata.xml,
so `mvn exec:*` failed with NoPluginFoundForPrefixException in the docker
publishing pipeline.
@yury-s
Yury Semikhatsky (yury-s) merged commit c17b606 into microsoft:main Sep 15, 2026
24 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants