R: Subclipse "Checkout as..." (strange?) working

I've read also the mail of Christian Buech (thank you!), which has this workaround:

1. checkout as...
2. when Eclipse has created the project folder and Subclipse asks you to
overwrite it open the project folder in Windows Explorer and copy all
the ".something" files somewhere else
3. let Subclipse do the checkout
4. copy those files back into the project folder
5. do a refresh in Eclipse

I apologize for the incompletness of my tests: I didn't verified the SVN client behaviour with files of same name already in the local directory.

Maybe for the Subclipse community this is not a big issue (you don't do a "checkout as..." every day), but my work group has to create quite a few new Eclipse projects sometimes, so for us it's not a trivial problem. And I think it can be a negative introdution to Subclipse for new users, because it's the first command you're likely to use.

If I'm right (at last!) the problem arises when you put in the repository the .something Eclipse files: in this case if you do a "checkout as..." and Subclipse don't remove preexisting files, the checkout fails. This takes care of one Subclipse use case (complete Eclipse project in the repository), but what about other case, when you already have source files (maybe from another ide) and you want to use them in Eclipse (the case I described in my first mail)?

So, what do you think about having a dialog box in the "checkout as..." command which asks the user what to do with Eclipse files? Maybe with a little explanation for new users (do you already have .something files in the repository? Delete files. Do you want to preserve Eclipse's .something files - AND you don't have any of them in the repository? Keep the local files).

Anyway, thank you for your support and for your very good work.

Best regards,

Fabio

-----Messaggio originale-----
Da: Mark Phippard [mailto:MarkP@softlanding.com]
Inviato: mercoledì 27 luglio 2005 20.58
A: users@subclipse.tigris.org
Oggetto: Re: Subclipse "Checkout as..." (strange?) working

Fabio Da Soghe <fabio.dasoghe@sysgroup.it> wrote on 07/27/2005 09:44:00
AM:

> If this is right, I don't understand why Subclipse deletes the just
created
> files (other then .project). Why not to simply checkout into the
> project

> folder, eventually overwriting file which are already present in the
> repository but without deleting anything (not only .project)?
>
> In this manner every type of newly created project should work fine
> with
the
> "checkout as..." Subclipse command.
> Actually in my installation (Eclipse/WTP) I'm not able to do a
> checkout
of a
> web application, using the Dynamic Web Project offered by WTP: I get
> the
files
> .classpath, .runtime and .wtpmodules deleted so Eclipse thinks it's a
normal
> Java project! And I don't know how to recreate the proper project
> files
once
> Subclipse has deleted them, nor I can figure out how to import my
sources from
> the remote repository in a new Dynamic Web Project.
>
> Could it be possible to change Subclipse behaviour when doing a
"checkout
> as...", as described above? I think it should improve Subclipse
usability and
> ease of project managing.

I have been doing some tests of this, and both Subversion command line and
TortoiseSVN error out on the checkout if there are any files or folders of
the same name as the checked out files.

That is why we work the way we do. There has been a patch floating around
the Subversion dev@ list to improve this. If the feature is added to
Subversion, then we could probably change this.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Jul 28 18:05:00 2005