Checking out projects multiple times, problems importing a large project

Hello!

Issue 1:

I fully appreciate the ability of Subclipse to check out projects into
an appropriate dir/project within Eclipse based on the .project files (I
assume this is how it works). However, I very often need to check out
the same project multiple times within a given workspace (for branch
management or temporarily working on a branch, for example). It seems
that the "Check out as..." functionality does not do what I would
expect...where the CVS module allows me to check out the same module
with a different name (and no prompting to specify what type of project,
etc) the Subclipse module requires me to specify it as a Java project,
set build paths, etc.

The intelligence to automatically check out /myproject/trunk and
/myproject/branch1 both as "myproject" without further intervention is
very cool...but it seems an additional option is needed for me to
specify a project name. Is this possible in the current code?

Issue 2:

I have had some trouble with Subclipse importing projects. Yesterday,
the first operation I tried with Subclipse was to import a large project
(4000+ files) into Subversion. After initially giving me an error, my
second attempt caused the Eclipse java process to just chug and chug and
chug at 100% CPU. The same CPU metric on the server was nominal. An
import using command-line CVS did not have any problems, and imported
all 4000 files fairly quickly.

I am running the most recent subclipse with JavaSVN under Eclipse 3.0
and subversion 1.1-ish on Gentoo Linux. I have been evaluating
Subversion as a possible successor to CVS at our organization, but
things like this prevent us from adopting it. We really must have
seamless Eclipse integration on par with the built-in CVS module, or
it's a no-go.

Thoughts?

--
Charles Oliver Nutter, Senior Specialist, System Architect
Ventera Corporation
Office: 612-370-3061     Mobile: 612-710-1274