Michael Tiller <mtiller@emmeskay.com> wrote on 03/06/2006 02:02:47 PM:
> I've been using Subclipse for a while but I'm working on a project now
> that includes a use case I haven't dealt with before.
>
> Imagine I've got a project that involves multiple repositories in a
> single project? I want to be able to commit and update to two separate
> repositories. What I'd like to be able to do is check out from one
> repository and put it in a one directory (e.g. srcbase1) and check
> something else out from another repository and put it in another
> directory (e.g. srcbase2). Ideally, I'd be able to commit and update
> from either of them.
You can do this, but not using the technique you described.
Subversion supports a feature called svn:externals that will let you do
this. Let's say you are checking out ProjectA, and it uses the code for
LibraryB. You can set a property named svn:externals on the folder for
ProjectA with a value like this:
src-LibraryB utl://to/libraryB/project
When you checkout ProjectA, it will create a project structure with all of
the source. You can then commit to both repositories.
You can basically set that property anywhere it makes sense within your
hierarchy. If you do not want to change ProjectA in this way, you can
create a third project that sets the svn:externals property to pull in
both projects. Sort of a "meta-project". It could even live in a 3rd
repository if necessary.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Mar 6 20:11:46 2006