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

Re: [Subclipse-dev] Working across projects (was: Changes to default

From: Jesper Steen Møller <jesper_at_selskabet.org>
Date: 2005-08-08 20:26:50 CEST

Mark Phippard wrote:

>Jesper Steen Møller <jesper@selskabet.org> wrote on 08/08/2005 01:39:11
>PM:
>
>
>>At work, we also often split our development into separate Eclipse
>>projects (just like with plugins) and it's annoying to have to see
>>changes peacemeal, but it's even worse to have to commit it peacemeal.
>>
>>To fix this for commits, in the case where the projects in question all
>>share a common root, the commit logic itself can handle this as a
>>special case (by iterating over all projects that need committing, group
>>

>>them by parents (if the parent is a WC of the same repository) and
>>execute the commit on a 'per-root' basis. This is a local fix which I
>>may look at some day soon.
>>
>>
>
>Unless I am wrong, the only way this could be done is if the common parent
>was checked out, outside of Subclipse, into a local folder. And the
>individual projects were then imported into Eclipse. Am I correct? I
>would love to see this feature implemented. I currently do this by
>committing outside of Subclipse when I want to do it.
>
>
>
Yes, that's how we do it. This way, we can update, commit, and switch
the entire product in the same place. Today, this would give us too many
revision numbers.

I also commit outside Eclipse to achieve this. I'll have a go at
implementing it at some point - the basis exists, but the interface to
SVNTeamProvider and CheckinResourcesCommand would need to change.

While looking at the CheckinResourcesCommand I've noted that it contains
two calls to commit. This is also a bad idea from a atomicity point of
view, since it can be optimized away in some quite common cases. I will
also look into this. Or mabye just post an issue for now.

-Jesper

>>To fix this for "Show pending operations", it could be made to work for
>>multiple resources (if it doesn't do this already), or perhaps to move
>>up to the workspace level (as an action in the view itself).
>>I don't know how difficult it would be to implement, but I guess it's
>>worth trying.
>>
>>Does anyone have any good ideas for this?
>>
>>
>
>I have never really even used this view. I was thinking of someday
>suggesting we dump it, but I probably never would :) No, I do not have
>any ideas how one would do this.
>
>
>
That view is excellent because it's small and fast compared to dealing
with Synch, and clearer re. what really changed compared with the
Navigator and/or Process Explorer, and it has easy access to diffing.

>Mark
>
>
>_____________________________________________________________________________
>Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
>_____________________________________________________________________________
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>
>
Received on Tue Aug 9 04:26:50 2005

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