slachiewicz opened a new pull request, #14092: URL: https://github.com/apache/maven/pull/14092
`mvn jar:jar deploy:deploy` on a pom-packaged project publishes the JAR as the `.pom` with maven-install-plugin 3.1.2 to 3.2.x and maven-deploy-plugin 3.1.2 to 3.1.4, and Maven gives no hint why. `MojoExecutor` now warns once, naming the mojo that set a non-POM file on the artifact with the POM's coordinates. Core cannot override that file on the Maven 3 API, so the fix itself is in the plugins (apache/maven-install-plugin#457, apache/maven-deploy-plugin#753); this makes the broken state visible. The check compares coordinates only, so it stays unaware of packagings and plugins, as #10481 requires. It warns rather than fails, because builds that run `jar:jar` on a pom project without publishing are legal today. Part of #10481 (MNG-8138); #14089 is the Maven 4 counterpart. Verified: `mvn jar:jar deploy:deploy` with maven-deploy-plugin 3.1.4 → 3.10.1 deploys the ZIP silently; this branch prints one warning naming `maven-jar-plugin:3.5.1:jar`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
