Paul Lorenz <plorenz@gmail.com> wrote on 01/30/2006 10:06:27 AM:
> On 1/30/06, Alexander Kitaev <alex@tmate.org> wrote:
> > Hello,
> >
> > > > 2. Add a filter to the packages view to only show files with
> > > > conflicts. Makes it easy(er) to find files you need to look
> > > at after a
> > > > merge. Adds dependency on some jdt plugins. Also depends on the
> > > > warnings stuff. It works by checking if there is a svn
> > > conflict merge
> > > > marker for the resource.
> > I would suggest making this dependency optional, otherwise Subclipse
will
> > only be limited to Eclipse IDE, and will not work with tools that are
built
> > on top of Eclipse Platform but does not include JDT plugins.
> >
> > I'm using "Problems" view for the same purpose - it allows to set up a
> > filter that only will show "SVN Conflict" kind of problems and also
provides
> > a "quick fix" actions to edit conflicts, mark file as resolved or get
remote
> > or local version of the file instead of merging.
> >
>
> I was worried about that. I hadn't realized there was a Optional
> checkbox on the dependencies.
I hadn't even noticed this in your original message. I have to admit this
makes me nervous. In the past I have had scenarios where I tried to use
optional dependencies and Eclipse would not install the plugin if the
optional dependency was not found. It could be that these issues have
been fixed. I will try to setup testing if it comes to that.
I agree with the general sentiment that we cannot make JDT a hard
dependency.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc 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 Mon Jan 30 16:39:25 2006