[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] RE: Implementing "check out into existing project"

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-08-09 22:56:40 CEST

"McHenry, Matt" <mmchenry@carnegielearning.com> wrote on 08/09/2006
04:41:38 PM:

> > Finally, if you wanted to implement that in Subclipse the hardest part
> is
> > going to be the local actions. You could not select the Project root
> or
> > src folder and do Team -> Commit/Synch/Update/ anything because that
> > folder is not a working copy. So you'd have to root out all code that
> > might make these assumptions and fix them. The actual checkout part
> would
> > not be too difficult, you would just need do the right validations and
> the
> > UI changes.
> What I haven't yet found in the code is where e.g. the Update
> command makes the assumption that a folder is a working copy. Maybe
> that's in UpdateResourcesCommand.run() where it just passes the File for
> the folder to ISVNClientAdapter.update(), but I don't yet understand
> enough to tell for sure.

You would probably mostly want to look at the action enablement code to
make sure the actions are not available unless the selected item is
managed. For many of the actions it probably already does this. This is
all done in the action classes in the UI plugin.

I think you are just scratching the surface though. I suspect the
FileModificationManager and all of the status and synchronize cache stuff
will be affected. You also have to come up with a way to handle the
decorators to be aware of this situation and present an alternate
decorator like CVS does.

You can probably checkout a "dummy" project using Subclipse so that it
gets connected to our team provider. Then close Eclipse and delete the
.svn metadata folders for the project and manually add in any managed sub
projects. Then restart the runtime, refresh the project and start dealing
with the problems. Once you have the major problems dealt with then you
can start tackling the UI of actually doing the checkout the way you


To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Wed Aug 9 22:56:48 2006

This is an archived mail posted to the Subclipse Dev mailing list.