maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Navarro (JIRA)" <>
Subject [jira] Commented: (MAVENUPLOAD-2335) Document best practices for Google Code hosted projects
Date Fri, 27 Mar 2009 01:17:12 GMT


Alexandre Navarro commented on MAVENUPLOAD-2335:

Is it possible to deploy with this technique with hg or git (or just a repo with http)?

> Document best practices for Google Code hosted projects
> -------------------------------------------------------
>                 Key: MAVENUPLOAD-2335
>                 URL:
>             Project: Maven Upload Requests
>          Issue Type: Improvement
>            Reporter: Eric Bottard
> 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
that there are some projects that use "svn" as a sync protocol, which is not documented at
> 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
> 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:
For more information on JIRA, see:


View raw message