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
--
Taylor Gautier
Product Manager
Terracotta, Inc.
Phone: +1 (415) 738-4053
Fax: +1 (415) 738-4099
Web: www.terracottatech.com
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
