Michael Tiller wrote:
> 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.
>
> This is not such a far fetched use case. Imagine you have Java packages
> that are stand-alone (can be used across projects) but you want to have
> access to them and potentially enhance them as part of some over-arching
> application?
To me, this use-case seems to differ from what you describe in the paragraph
above. So maybe I don't really understand what you are trying to accomplish.
Anyway: for example the Tomcat source consists of "stand-alone-like" modules
which reside in seperate directories. To be able to pull all those
directories with a single command, Subversion's "svn:externals" property is
used on an (otherwise empty) directory:
Look at the properties of this
http://svn.apache.org/repos/asf/tomcat/current/tc5.5.x
repository to see what I mean.
svn:externals is described here:
http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html
Maybe that's what you're looking for.
Regards
mks
---------------------------------------------------------------------
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:17:03 2006