jira-importer commented on issue #306: URL: https://github.com/apache/maven-install-plugin/issues/306#issuecomment-2771866617
**[Robert Lieske](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=robert12345)** commented ok, I wrote there: I commented on your merge commit. In the meantime I found out, that the uploaded POM does not have the content I want, so I need to fix this first, so that I can provide a corrected sample for my use case. Nevertheless (regardless what my motivation is to disable POM generation), the current versions of the maven-install-plugin and maven-deploy-plugin do not behave as documented here https://maven.apache.org/plugins/maven-deploy-plugin/examples/disabling-generic-pom.html. To describe my motivation (copied from the other bugreport https://issues.apache.org/jira/browse/MINSTALL-156): I want to deploy both the created JAR and the JAR-with-dependencies to the repository. As the release repository does not allow to upload the same POM twice, I have to configure the maven-deploy-plugin to skip generation of POM when uploading the JAR-with-dependencies. As a side note: the uploaded artifacts have to have a different name, so I need to configure everything by hand. and: I have updated my sample to fix the issue with the content of the POM (artifact name differs from filename). Basicly you missed the point, that the uploaded artifacts should have a different name. I have changed the code upload a released version, so you'll see the problem (overwriting uploaded POM is not allowed), when you change the plugin-version to 3.0.0-M1. To make the sample work for you, supply 'releaseRepositoryUrl' and 'releaseRepository' with credentials in your settings.xml -- 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
