On 7/11/07, Matthew Hannigan <mlh@zip.com.au> wrote:
> On Wed, Jul 11, 2007 at 03:06:32PM -0400, Mark Phippard wrote:
> > > [ ... ]
> > >The dependencies don't form a tree, which is why they are in separate
> > >modules like above. Doing it this way keeps everyone from needing to get
> > >every directory, so let's say a developer of project A might have 3
> > >separate checkouts:
> > >
> > >/Dev
> > > - /AppA (from AppA/trunk)
> > > - /LibA (from LibA/trunk)
> > > - /LibB (from LibB/trunk)
> > > [ ... ]
>
> > See this issue:
> >
> > http://subversion.tigris.org/issues/show_bug.cgi?id=2381
> >
> > It includes a link to a hacky workaround. Basically checkout an empty
> > folder somewhere and copy its .svn folder to /Dev. This gets by the
> > checking that SVN does to see if there is a common WC.
>
> Curiously enough I get commits from Eclipse users which have commits
> from different WCs (projects in eclipse parlance)
>
> I guess Eclipse (well, actually subclipse) must do something like the
> hacky workaround automatically?
The next major Subclipse release will do the hacky workaround. The
current version it works for people that choose to use the pure Java
SVNKit client option. That has a method that handle this situation
and Subclipse is coded to use that method when SVNKit is used.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 12 01:06:41 2007