[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 preferences)

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-08-08 19:51:23 CEST

Jesper Steen Møller <jesper@selskabet.org> wrote on 08/08/2005 01:39:11
PM:

> On the preferences change, Greg Irvine wrote:
>
> >>3) Turn off the text decorators (for showing changes. not the info
parts)
> >>
> >>
> >Is this the ">" that shows if a file or somewhere below in the
directory
> >tree is changed? If so, I find it extremely useful when looking for
changes
> >because our application is plugin based and each plugin is a separate
> >eclipse project, and hence "show pending operations" isn't useful if
i've
> >made changes across a couple of projects.
> >
> >
> This touches a personal gripe of mine, handling changes across projects.

> 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.

> 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.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Tue Aug 9 03:51:23 2005

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