news <email@example.com> wrote on 04/07/2005 03:39:42 PM:
> On Thu, 07 Apr 2005 14:25:55 -0400, Mark Phippard wrote:
> well, actually for one reason I just like having all the projects I'm
> working on in one directory (as they are modules and components of a
> bigger web project, it's easier to set CDPATH and work on them in one
The Eclipse feature I am describing does the exact same thing, it just
doesn't use symlinks. I can create a WC with a bunch of projects checked
out into it. In Eclipse when I import them it is essentially just
"registering" them to my workspace. Nothing moves. With Eclipse 3.1 and
Subclipse 0.9.29 when you do this it will even automatically "share the
project" with Subclipse. Also, if you add a new project and you place it
in this master WC location, it will even auto-add it to Subversion for
> And the project root itself has several symlinks pointing around in it
> (common pieces among multiple installs etc..), but after manually
> Resolving all of the symlinks (about 3 or 4), subclipse auto-magically
> detected the project after closing and re-opening it.
> Is there any reason why you don't resolve the symlinks in subclipse? Or
> least "CD" into the directory? as I just checked and if I trun
> svn status PrintTicket from the main project dir (referencing the
> it fails. but changing into the PrintTicket directory and running svn
> status works fine.
Subclipse itself doesn't really do anything with your files and folders.
We just make Subversion API calls. Subclipse should not be in the
business of figuring this stuff out. Bring it up on the Subversion
mailing list and convince them to make the API follow the symlink.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Fri Apr 8 05:47:29 2005