michaelboyles commented on PR #3: URL: https://github.com/apache/maven-deploy-plugin/pull/3#issuecomment-2162794307
My use-case is that I generate a Spring Boot fat JAR with `spring-boot-maven-plugin:repackage`, then I ZIP that together with a bunch of scripts etc. with `maven-assembly-plugin:single` to create a final ZIP. The ZIP is the thing I want to deploy, and I don't want to deploy the Spring Boot JAR. I can skip attaching the fat JAR (the plugin supports `<attach>false</attach>`) but all that does is leave the original JAR attached from `maven-jar-plugin`. There is no configuration to not attach that, and even if there was, there's a good chance doing so would break the Spring Boot plugin. I just want a simple way to tell deploy-plugin, "don't deploy something". I don't want to go down a rabbit hole trying to stop stuff being attached in the first place. I could imagine a world where someone wants an artifact to be install-able but not deploy-able. In which case, not attaching the artifact is not a solution. @khmarbaise Can you please comment on this? You wanted a real-world use-case, and 5 people have now given you theirs. It's disappointing that a PR has been ready to go for 6 years and is still sitting here. I checked through it and it looks like a high-quality change. It has tests and updates to documentation. I'm happy to fix the conflicts. -- 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]
