Paul Lorenz <email@example.com> wrote on 01/27/2006 03:12:45 PM:
> On 1/27/06, Mark Phippard <firstname.lastname@example.org> wrote:
> > Paul Lorenz <email@example.com> wrote on 01/27/2006 01:35:41 PM:
> > > Ok, I missed that. We have a couple thousand warnings in our project
> > > (working on cleaning them up, buts it's a slow process), so they
> > > easy to miss. I'm still going to look at having those show up in the
> > > conflicts view, because they are conflicts, and it's (IMO) the
> > > place to look for them :) Actually right now, I'm not sure how
> > > anything ever shows up in the conflicts view for subclipse.
> > If you want to pursue that, go ahead, but I think it is a big mistake.
> > There is very little, if any, relationship between a Subversion
> > and a Synchronize view conflict. I do not see how you can reconcile
> > two.
> How would you feel about a separate view that listed conflicts and
> would bring up the Edit Conflict when you double clicked an entry?
Does the existing SVN Pending Operations view not essentially already
fulfill this need? I have no objections to enhancing this view, but
adding another view would not be a good idea.
> If not that, how about a checkbox somewhere to make merge conflicts
> show up as errors instead of warnings in the problem view?
We chose warning for a couple reasons:
1) Usually the conflicts muck up the source so the source will already
have errors and an error decorator. It looked weird to have two error
2) Our menu icons for Mark Resolved and Edit Conflicts already
incorporated the Warning decorator.
I wonder if Eclipse provides a way to contribute filters to a view so that
the view drop down could let you pick various SVN filters to only show
items in certain states? Then you could use these in things like the
Navigator or Package Explorer views to filter the list.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jan 27 21:30:26 2006