Eclipse itself has some limitations with projects that are actually in the
workspace directory, so I don't think you are going to get your desired
layout of <workspace>/projA/<projects> and <workspace>/projB/<projects>.
Specifically, you can only import existing projects in the workspace
directory if the project name is identical to the the directory name and an
immediate child of the workspace.
As far as the "cannot create project to checkout to" errors, the CVS import
wizard won't even let you get that far with a location under the workspace
(their dialog shows the "Cannot overlap workspace location error"). The New
Project wizard, with no Team involved, won't let you create a new project
I would guess that Subclipse should probably be checking for this, too, so
maybe an issue should be filed for it?
On 4/13/06 2:01 AM, "Gary McWilliams" <firstname.lastname@example.org> wrote:
> -----Original Message-----
> "Gary McWilliams" <email@example.com> wrote on 04/12/2006
>> checkout projA/trunk/* into <my_workspace>/projA (and have all of the
>> trunk eclipse projects in one place) and checkout projB/trunk/* into
> In my original mail, I have in fact 2 separate repos that I want to work
> with within one workspace. Each of these has a (set of) "common" folders
> (e.g. a www folder, an ivy-conf folder; the contents of these is
> specific to each repo's projects, but we use a common project structure
> for all work we do - if that helps explain anything; specifically why I
> need to create these projects within sub-folders in the workspace).
A common solution is to just avoid putting projects in the workspace
directory. So if I had two big projects A and B with multiple eclipse
projects under them, this is what my directory structure ends up looking
<my_workspace (could go here)>/
<Big Project Directory>/
<my_workspace (or here)>
So you could use the repo browser to check out all the Projects in
projA/trunk, but specify <Big Project Directory>/projA as the location
instead of something under the workspace.
Or you you could use an external client to check out all of projA, with the
command line, for example:
svn co http://<repo>/projA/trunk/ <Big Project Directory>/projA
Then "Import Existing Projects" should work just fine, and if you are using
3.1, should be shared automatically.
I think this will get you pretty close to your desired layout. I started
using something like this to get around a bug in subclipse (#220, fixed now,
thanks to Mark), but I now prefer it this way because there are quite a few
* I have fewer workspaces by adding more projects like A and B (and using
working sets) so I don't have set things like code style/editor settings
over and over again, or
* you could have multiples workspaces which mix projA, projB, projC, etc.,
with only 1 working copy for each
* if projA/ is a working copy, you can use another svn client to switch the
whole group at once
As Mark mentioned in another message, if there is something that needs to be
shared in <Big Project Directory>, you should be considering svn:externals
and external (to eclipse) subversion clients.
Antony Saba, firstname.lastname@example.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Apr 13 16:50:56 2006