I'm just another user like yourself, but I agree with you there didn't
seem to be a way to do this using the Checkout from SVN wizard. I got
the same behavior even when I did the checkout with Tortoise, and then
followed it up with the Eclipse import... Existing Projects into
Workspace. That import wizard seemed to ignore the existing .project
file and give the project it's name based on the folder name.
You might also post to the Eclipse community and see if they have any
more suggestions going the import route. At least with import, you could
do a batch of projects, as you seem to be suggesting you are doing.
Web Applications Developer, Sogeti USA
From: Charlie Floss [mailto:CFloss_at_pscufs.com]
Sent: Wednesday, June 25, 2008 12:16 PM
Subject: [Subclipse-users] Checkout in subclipse renaming folder...
When I check out code from my project with TortoiseSVN I
get folder names that were in the repository.
folder1 --contains an eclipse project called EclipseProj1
folder2 --contains an eclipse project called EclipseProj2
folder3 --contains an eclipse project called EclipseProj3
With TortoiseSVN when I check out to a
workspace folder I get in my checkout folder
With subclipse when I check out to a
workspace folder I get
Basically when subclipse is checking out the project it
notices the .project file and uses the name in the .project file for the
folder name and not the name of the folder that was in the repository.
I would like to have it check out using the repository folder name in
the file system but recognize the .project name for the name that is
shown in eclipse.
I can checkout using TortoiseSVN and then import all the
checked out code into eclipse but it would be nicer just to checkout in
subclipse and have it not rename the file system folder to match the
Is there any way to have subclipse check the code out
like TortoiseSVN does it and then add the project in eclipse picking up
what is in the .project file as the project name in Eclipse?
This e-mail is intended for the addressee shown.
It contains information that is confidential and
protected from disclosure. Any review, dissemination
or use of this transmission or its contents by persons
or unauthorized employees of the intended organizations
is strictly prohibited.
The contents of this email do not necessarily represent
the views or policies of PSCU Financial Services.
Received on 2008-06-25 19:36:32 CEST