Thinking a bit more about this, I don't think we need anything fancy & fully dynamic like new entry points for SCM types. Since Google Code only has SVN, git and hg, we can reference those tools directly. Just catch ImportErrors so they're all optional.
--- ** [tickets:#6463] Create code importer for Google Code** **Status:** code-review **Labels:** import google-code **Created:** Mon Jul 15, 2013 04:31 PM UTC by Cory Johns **Last Updated:** Tue Jul 23, 2013 03:48 AM UTC **Owner:** Tim Van Steenburgh During project import, SCM needs to be included. Since Google Code only supports a single repository at a time, we should just have a single Code Importer that checks the project to discover the repo type and passes that information to the appropriate SCM tool's `clone_from_url` method. One way to discover the repo type would be to load `https://code.google.com/p/%s/source/browse/` and get the text of the item `id="crumb_root"`, which will be one of `" git/ "`, `" hg/ "`, or `" svn/ "`. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
