[news.eclipse.tools] Re: 2.0.1 feature change

["Bob Foster" <bob@xxxxxxxxxx>]

"Harald Niesche" <harald@xxxxxxxx> wrote in message
news:alqhh9$s52$1@xxxxxxxxxxxxxxxx
> "Peter Manahan" <manahan@xxxxxxxxxx> wrote in message
> news:3D80A450.8040308@xxxxxxxxxxxxx
> > Seems the PDE is working as designed. The plugin.xml is driving the
> > classpath not the source code.
>
> Right, that's the way it works.
>
> > I don't know about you but i tend to code
> > then add the jars when it doesn't compile. I rarely know/care which jars
> > up front I need. I tend to modify the plugin.xml last rather than first.
> > The PDE assumes you modify the plugin.xml before you code which IMO is
> > backwards.
>
> But that doesn't solve Bob's Problem with 2.0.1 and  2.0 while using
> plugin.xml does. Plus I find it easier to add a required plugin to my
> plugin.xml using the editor rather than browsing for the Jar in the Java
> Build Path Property Page...
>
> Just accept that in a PDE project you manipulate the classpath through the
> plugin.xml, don't try to work against it (you are bound to lose this fight
> ...)

I know what Peter is talking about. Once a project has gotten itself into
this state (whatever it is), it can't get out. Update Classpath is purely
destructive. Adding things to plugin.xml has no effect on the classpath.

> Maybe the PDE should make it easier to edit this part of the plugin.xml
> through a property page in the project properties.

Gosh, I think I can edit the plugin.xml. ;-} That's not the problem.

Bob

> Harald
>
>