You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Diggory (JIRA)" <ji...@codehaus.org> on 2007/11/07 04:01:35 UTC
[jira] Created: (MAVENUPLOAD-1798) Need to move rsync to different
host than sourceforge
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 <ds...@lists.sourceforge.net>"
MODE=rsync_ssh
FROM=mavensync@maven.dspace.org:/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
[jira] Commented: (MAVENUPLOAD-1798) Need to move rsync to
different host than sourceforge
Posted by "Mark Diggory (JIRA)" <ji...@codehaus.org>.
[ 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 <ds...@lists.sourceforge.net>"
> MODE=rsync_ssh
> FROM=mavensync@maven.dspace.org:/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
[jira] Commented: (MAVENUPLOAD-1798) Need to move rsync to
different host than sourceforge
Posted by "Mark Diggory (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114154 ]
Mark Diggory commented on MAVENUPLOAD-1798:
-------------------------------------------
Thanks Carlos,
Yes we could have, but I'm working more towards us maintaining our own infrastructure and this will allow us to keep a canonical copy locally in our own repository for posterity. Someday soon we do expect to leave S.F. behind.
Cheers,
Mark
> 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
> Assignee: Carlos Sanchez
>
> 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 <ds...@lists.sourceforge.net>"
> MODE=rsync_ssh
> FROM=mavensync@maven.dspace.org:/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
[jira] Closed: (MAVENUPLOAD-1798) Need to move rsync to different
host than sourceforge
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez closed MAVENUPLOAD-1798.
---------------------------------------
Assignee: Carlos Sanchez
Resolution: Fixed
you could have deleted old artifacts from the sf repo as they got synced
> 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
> Assignee: Carlos Sanchez
>
> 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 <ds...@lists.sourceforge.net>"
> MODE=rsync_ssh
> FROM=mavensync@maven.dspace.org:/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
[jira] Commented: (MAVENUPLOAD-1798) Need to move rsync to
different host than sourceforge
Posted by "Mark Diggory (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113023 ]
Mark Diggory commented on MAVENUPLOAD-1798:
-------------------------------------------
I've also encountered a syncronization issue the following artifacts are not getting added to the central repo
http://dspace.sourceforge.net/repository/release/org/dspace/xmlui/jakarta/jakarta-bcel/20040329/
should be at
http://repo2.maven.org/maven2/org/dspace/xmlui/jakarta/jakarta-bcel/20040329/
it is also available in the new repository location at
http://maven.dspace.org/release/org/dspace/xmlui/jakarta/jakarta-bcel/20040329/
I'm concerned that because the release looks like a "date" its not getting transfered. However, this is a stable release of this dependency for our project.
We are encountering the same issue for
http://repo2.maven.org/maven2/org/dspace/xmlui/jcs/jcs/1.2.5-dev-20050313/
http://dspace.sourceforge.net/repository/org/dspace/xmlui/jcs/jcs/1.2.5-dev-20050313/
http://maven.dspace.org/release/org/dspace/xmlui/jcs/jcs/1.2.5-dev-20050313/
thanks for any advice,
Mark Diggory
> 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 <ds...@lists.sourceforge.net>"
> MODE=rsync_ssh
> FROM=mavensync@maven.dspace.org:/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