slachiewicz opened a new pull request, #754:
URL: https://github.com/apache/maven-deploy-plugin/pull/754

   On a pom-packaged project, `jar:jar deploy:deploy` under Maven 4 deploys the 
JAR as `test-1.0-build.pom`. `createDeployerRequest` set the POM artifact's 
path only when the artifact manager had none, and after `jar:jar` it already 
has one: the JAR. This sets the path unconditionally, as `InstallMojo` on 
`maven-install-plugin-4.x` does. It is the 4.x counterpart of #753.
   
   The new IT `deploy-pom-after-jar` asserts that every deployed `.pom` is this 
project's POM and not a ZIP.
   
   Verified: `mvn -Prun-its verify -Dinvoker.test=deploy-pom-after-jar` on 
4.0.0-rc-7 → fails without the fix (`test-1.0-build.pom is a ZIP, not a POM`), 
passes with it.
   


-- 
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]

Reply via email to