Any subversion experts out there?

[david-8uUts6sDVDvs2Lz0fTdYFQ at public.gmane.org (David Kramer)]

> I just read up on svn:externals. I think that will do the trick. Thanks!

Seconded.  Bringing shared components into a project is one of the most
popular uses for svn:external.

Let me give you a piece of advice we learned the hard way in my company:
Do not have the external point to the trunk of the shared component.  Make
a release/X.Y directory, and point it at that directory.  As you release
new versions of the shared component, you can test each app with the new
version, and change the svn external to point to the newer version.

If you don't do it this way, when you update the shared component for one
application, all the others will be forced to work with the new version. 
If there's an API change, you're sunk.  But if you create releases of the
shared component and link to them from the applications, the work for one
application can't break another.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.