[
http://jira.codehaus.org/browse/MAVENUPLOAD-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MAVENUPLOAD-2335.
---------------------------------------
Assignee: Carlos Sanchez
Resolution: Won't Fix
I started syncing from svn as a test and then grew up, not the preferred way
but works, with a little more work
for questions, please go to [email protected]
> Document best practices for Google Code hosted projects
> -------------------------------------------------------
>
> Key: MAVENUPLOAD-2335
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2335
> Project: Maven Upload Requests
> Issue Type: Improvement
> Reporter: Eric Bottard
> Assignee: Carlos Sanchez
>
> Not sure this belongs here or on some dedicated mailing list, but for
> projects hosted at Google Code (or any non-rsync capable hosting services),
> the best practices for having a release go to central are unknown.
> I see at
> http://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv
> that there are some projects that use "svn" as a sync protocol, which is not
> documented at http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
> This would be a perfect fit (although less enjoyable on your side I guess)
> for Google Code projects, as many of them maintain a repo in their svn.
> As an example, see http://liquidform.googlecode.com/svn/maven-repo/releases/
> Any other best practices or advice would be welcome
--
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
