Juris Galang wrote:
> we're using svn:externals it with our Enterprise code-line, it works -
> but it's a pain since an external is tied to a specific revision.
That is true, but the default revision is HEAD so that updates in the
external repository will be automatically pulled in when you do an svn
update.
If you do choose to use an svn:externals definition, you should probably
use the http URL for the value of the svn:externals property instead of
https. If you used the https URL there would be no way of getting a
read-only checkout of your project without having a Subversion account.
This would mean, though, that you would have to have a separate
working copy to make commits to the external project. I've heard
something about future Subversion releases supporting "relative"
svn:externals definitions, but for now at least you must specify the
full URL.
--
Jason Voegele
If you think education is expensive, try ignorance.
-- Derek Bok, president of Harvard
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
