[
http://jira.codehaus.org/browse/MAVENUPLOAD-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113268
]
Mark Diggory commented on MAVENUPLOAD-1798:
-------------------------------------------
Please disregard the previous comment. We determined the correct
name-versioning convention for setting up these artifacts as releases and have
them transfer to the central repository.
However, we do still require the rsync source to be changed.
thanks you,
Mark Diggory
DSpace Commiter
> Need to move rsync to different host than sourceforge
> -----------------------------------------------------
>
> Key: MAVENUPLOAD-1798
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1798
> Project: maven-upload-requests
> Issue Type: Improvement
> Reporter: Mark Diggory
>
> Apparently our artifacts are simply too big and numerous to be supported in
> the SF group directory, instead we will be hosting our own remote repository.
> I configured the mavensync user with the public key and it should now be
> available for login.
> #!/bin/sh
> CONTACTS="DSpace Developers <[EMAIL PROTECTED]>"
> MODE=rsync_ssh
> [EMAIL PROTECTED]:/var/maven/release
> GROUP_DIR=org/dspace/
--
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
