jira-importer commented on issue #468: URL: https://github.com/apache/maven-deploy-plugin/issues/468#issuecomment-2771543564
**[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** commented Have you bound deploy plugin in your pom with the `deploy-file` goal several times which means you can call simply `mvn clean deploy` and that's it? If so you are violating the separation of concerns of a pom file cause a single pom file should have only one concern which means produce a single artifact (identified by groupId, artifactId, version) or maybe several but having the same dependencies...If you need to have different dependencies this means you should have different pom files. Sorry to say if your customers are not familiar with slf4j than they should read the manual...but I can understand that you like to offer them a convenient solution which can simply being done by using different pom's with a single concern which in result produces a multi module build. Based on others requests..This issue is open for a long time and last comment is of 2014..more than two years silence so it couldn't be real big problem..apart from that there clean solutions for this which I already described... -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
