You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Harald Kuhr (JIRA)" <ji...@codehaus.org> on 2007/02/28 12:04:44 UTC

[jira] Commented: (MDEPLOY-48) deploy:deploy-file does not support deploying sources jars too

    [ http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88756 ] 

Harald Kuhr commented on MDEPLOY-48:
------------------------------------

It's possible to upload sources via the -Dclassifier=sources switch, the problem with this is it bumps the build-version of snapshots.. So I can't have sources and classes of the same version. 

A workaround is to manually rename the jar, sha and md5 to the latest version after update, but it is of course not a very elegant solution...

Had a chat with Trygvis last night and he told it should be an easy thing to fix, so I'll expect it done by tomorrow. ;-)


> 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