jira-importer commented on issue #468: URL: https://github.com/apache/maven-deploy-plugin/issues/468#issuecomment-2771543577
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented Hi Richard, I think we need to cool down things. When reading your story for the first time I had the same idea as Karl Heinz. I consider suggesting a solution which matches the current Maven behavior as a great help. Reading your situation over again, I see your situation: 1 sourceproject results in multiple artifacts (jar + pom), meaning different artifactIds. I think the situation is too rare to apply the patch. A custom plugin makes more sense. Maybe there's good news: [stephenconnolly](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephenconnolly) is working on a proposal for the next major version of Maven. And one of the suggestions is to have a pom for every uploaded artifact. Mapping this to your situation you **could** attach every artifact with the same artifactId, but with a separate classifier. Another option I'm thinking of right is to have multiple pom-files if the root of your project. Maybe even with an aggregator pom.xml (aggregator with modules pointing to every pom below) pom-default.xml pom-jcl.xml pom-jul.xml this way there's no need for multiple separate calls, no need for separate commandline arguments. -- 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
