It depends.
svn:externals is the right way to do it when you want your project's
dependencies to be the latest version. For a lot of projects though,
it's better if the dependencies are frozen most of the time and only
sync'd occasionally when the dependency reaches a new stable state. In
these cases it's best to "svn cp" the version you want into your project
try and then do merges from mainline as needed.
Meme Bag wrote:
> I'm curious about popular approaches Subclipse users take to the issue
> of multiple products built from the same code base. When I used CVS
> in the past I did the same thing I'm doing with SourceSafe (ant
> fetching different CVS directories under the current working directory.)
>
> How do Subclipse users share source code among multiple products? Do
> they build different subsets of a single Subversion tree in each
> Eclipse project?
>
> */Jeff Bowden <jlb@houseofdistraction.com>/* wrote:
>
> This is a subclipse issue. If he didn't need eclipse/subversion
> integration then his ant script could just do the checkouts and
> eclipse
> and subversion would deal with things just fine by themselves. It's
> true that the 'correct' subversion way to do things is to use
> svn:externals but it would sure be nice if subclipse could
> transparently
> handle subdirectories with different URLs.
>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Better first dates. More second dates. Yahoo! Personals
> <http://us.rd.yahoo.com/evt=27808/*http://personals.yahoo.com>
Received on Tue Apr 5 08:53:47 2005