jira-importer commented on issue #525: URL: https://github.com/apache/maven-deploy-plugin/issues/525#issuecomment-2771548913
**[Omar Ahmad](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=omar952)** commented Hi, Could this please be reopened? I have come across this issue in a different scenario. The scenario I have is the following: 1. I have release artifacts inside nexus and the releases repository does not allow redeployments of artifacts. 2. These release artifacts were not uploaded with sources and javadocs at the time of the release. 3. I would like to upload sources and javadocs by syncing to the tag in SCM, and running the following maven command: ``` mvn -e org.apache.maven.plugins:maven-source-plugin:2.4:jar org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy-file -Dfile=${project.build.directory}/${project.artifactId}-${project.version}-sources.jar -DrepositoryId=deployment -Durl=http://nexus-ip:8081/nexus/content/repositories/releases -DgroupId=${project.groupId} -DartifactId=${project.artifactId} -Dversion=${project.version} -Dclassifier=sources -Dpackaging=jar -DgeneratePom=false ``` Note, I am running this against a multi module project and so hence the reason for using ${project....} properties. The result of running the command above is that the sources JAR is created and uploaded successfully, but the build fails as maven attempts to deploy the same sources JAR a second time which gets rejected by nexus as the repository is set to not allow redeployments. Any suggestions or thoughts? Is there another way that I could deploy sources and javadocs to existing artifacts inside nexus? Thanks, Omar -- 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
