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

["Bob Foster" <bob@xxxxxxxxxx>]

Sorry to keep this going, but I'm really missing something.

I have the dependencies set up correctly in plugin.xml. But I can't get
those to automatically get added to the build path. Have to do that
manually. What's the secret?

Bob

"Harald Niesche" <harald@xxxxxxxx> wrote in message
news:alo8ff$mjq$1@xxxxxxxxxxxxxxxx
>
> "Bob Foster" <bob@xxxxxxxxxx> wrote in message
> news:alo459$jtt$1@xxxxxxxxxxxxxxxx
> > "Harald Niesche" <harald@xxxxxxxx> wrote in message
> > > Exactly which variables are those?
> >
> > Look at the source properties for plugins you depend on. Those
variables.
>
> Okay, that was just a misunderstanding -- there are no new or changed
> variables, it's the variable extensions that are different. (Sorry about
my
> nitpicking, I really didn't understand :-)
>
> > You get "Update Classpath" to do something useful? The only thing I've
> ever
> > seen it do in a plugin project is rip out all the build dependencies,
> > requiring me to re-add them by hand. (I tried this again in 2.0.1.) What
> am
> > I doing wrong?
>
> It sounds like you are adding required external classes manually. As far
as
> I understand the plugin classloader stuff, you need to name all entries of
> your classpath in the plugin.xml -- either as "Dependencies", plugins your
> plugin requires or under "Runtime", parts of your plugin classpath (that
can
> be exported if you wish).
>
> This works quite nicely for me, I only regret that I checked in the
> .classpath file.
>
>
> Harald
>
>
>