jira-importer commented on issue #593:
URL: 
https://github.com/apache/maven-deploy-plugin/issues/593#issuecomment-2771593105

   **[Bob 
Fields](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bfields)** 
commented
   
   Problem still exists, and the -DuniqueVersion=false workaround sortof works, 
however if you are pointing to an existing pom file for the initial deploy, and 
then point to the same pom file for the -sources deploy, the -sources.jar 
archive is deployed, however it gives an error when trying to deploy the pom 
file again (correctly): [INFO] Error installing artifact's metadata: Error 
while deploying metadata: Failed to transfer file: http://xxx.pom. Returncode 
is: 400. Workaround is to specify the -DGAV individually, instead of the pom.
   
   I know there's a way to tell it not to generate a pom. Is there a way to 
tell it not to deploy the pom (since it already exists), but still be able to 
use the GAV information contained in the pom instead of specifying all on the 
command line? Or better yet, add the options to specify a sources and javadoc 
archives at the same time as the runtime deploy.
   


-- 
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]

Reply via email to