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

   Adds `skipAttachedArtifacts` to the `deploy` goal: a list of selectors 
(`groupId`, `artifactId`, `classifier`, `extension`) for attached artifacts 
that stay out of the deployment, such as a shaded or executable JAR that only 
other modules of the build need. The main artifact, the POM and the consumer 
POM of Maven 4 are never selected, and an entry that matches no attached 
artifact fails the build, so a misspelled entry cannot publish what it was 
meant to hold back.
   
   This carries the idea of #3 by @xleon90, whose 2018 patch no longer applies 
to the current code. The commit has a `Co-authored-by` trailer: merge with 
"Rebase and merge", or keep the trailer when squashing. Unlike #3, an entry 
takes no version and may leave out any coordinate.
   
   With `deployAtEnd` the mojo of the last module deploys every module, so each 
module's selection is made in its own execution and kept in its plugin context; 
the `skip-attached-artifacts` IT covers a build where only the first module 
skips. The same change for 4.x is #755.
   
   Verified: `mvn verify -Prun-its` on Maven 3.9.16 → 64 tests and 13 ITs pass 
(1 skipped by Maven version); the new IT and the unit tests also pass on 
4.0.0-rc-7.


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