[
http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234786#action_234786
]
Bob Fields commented on MDEPLOY-48:
-----------------------------------
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.
> deploy:deploy-file does not support deploying sources jars too
> --------------------------------------------------------------
>
> Key: MDEPLOY-48
> URL: http://jira.codehaus.org/browse/MDEPLOY-48
> Project: Maven 2.x Deploy Plugin
> Issue Type: Improvement
> Affects Versions: 2.3
> Reporter: Geoffrey De Smet
>
> deploy:deploy does, but deploy:deploy-file doesn't have a parameter to tell
> him where the sources jar is:
> mvn deploy:deploy-file -Dfile=$artifactFile -DpomFile=$pomFile -Durl=$toRepo
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
