jira-importer commented on issue #468: URL: https://github.com/apache/maven-deploy-plugin/issues/468#issuecomment-2771543582
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented `deploy-file` is designed for uploading artifacts of which you only got the files. By uploading these files you can make them available as dependencies. These jars come from a third party and you want to deploy them to your repository, so providing a URL makes sense. If you have the sources and these are packaged to an artifact, then there's a clear build lifecycle. In this case you should make use of the `deploy` goal. Your situation matches the latter, so there should be +no+ need to use `deploy-file`. Abusing `deploy-file` is code-smell to me. Allowing such hacks tend to lead to the old ant-buildmaster, where only one or a few understand what's happening by the build tool. Maven says: a pom/GAV can only have main artifact. If you have multiple main artifacts, you should have more pom.xml files. That's something everybody will understand. If one pom.xml generates multiple main artifacts with different GA's a lot of people will be confused. I'm willing to think of a solution, but not by letting the `deploy-file` goal use the default repository. So no matter the number of lines, the patch or the number people who are interested, the code-smell is really bad so there must be a better solution. -- 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
