rvesse commented on pull request #3: URL: https://github.com/apache/maven-deploy-plugin/pull/3#issuecomment-734331457
Another practical use case, due to the constraints of our CI/CD system some of our projects use Apache Maven as the overarching build tool but use plugins to invoke other tools - `docker`, `helm`, `rpmbuild` - to package non-Maven things based upon our Maven build outputs. For example we have modules with packaging type `war` that will also package the built `war` into a Docker image with Jetty when an optional profile (`-Pdocker`) is activated. Then for ease of integration testing within our large multi-modules builds we have these plugins attach Maven artifacts as well, this lets us then have other modules depend on those artifacts explicitly to enforce required module build order and that the developer activated the right profile. *BUT* we don't actually want to deploy these attached artifacts because the original artifacts e.g. the Docker images themselves are going to get deployed by non-Maven post-processing steps to their own appropriate repositories provided as part of our CI/CD system. TL;DR We use Maven to build non-Maven artifacts (e.g. Docker images) that don't want/need to be deployed to our Maven repository ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
