I think we should support http:// in the future. Seems like it would be annoying to restrict to a file path at this point given that it's been a url till now and will (hopefully) support a url in the future.
I guess I'd vote for supporting both. It's easy enough to detect whether something is a url and just retry as a file path. Alex ----- "Taylor Gautier" <[EMAIL PROTECTED]> wrote: We've run into some issues with the repository spec being a uri rather than a file path. It has been pointed out that really we only support repos in a filesystem anyway, so a uri is overkill, and in fact could lead someone to believe we support something like http:// or worse gopher://, which is not the case. So I think it would be best to convert this setting to a file path, which is more consistent with the rest of our config anyway. Thoughts? What consequences will this have? I suspect the maven plugin uses the repo setting, but at the system level by setting -D... Maybe we need to implement this with a backward compatible translation from a file url to a file path? http://jira.terracotta.org/jira/browse/CDV-685 _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
