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

["Harald Niesche" <harald@xxxxxxxx>]

"Bob Foster" <bob@xxxxxxxxxx> wrote in message
news:alokau$run$1@xxxxxxxxxxxxxxxx
> Sorry to keep this going, but I'm really missing something.

Don't apologize, I'd be doing the same ...

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

I guess an example would be in order -- what is it, that disappears and
where in the plugin.xml do you mention that?

Since it simply worked for me from the beginning, I have no idea what could
be wrong -- maybe you need something in there that I don't ...

OK, I have tons of plugins I depend on (mostly because I have been looking
at the plugin source to find out how to use stuff). I have one src folder
and I tried adding a lib/blah.jar (to the "Runtime" tab), just to see,
whether that works as well.

I have turned on all the checkboxes under Preferences | Plug-In Development
| Java Build Path Control (because I didn't turn any of them off).

The "Source Code Locations" tab has four variables pointing at different
org.eclipse.*_2.0.1\src folders, because I'm at home where I have Eclipse
2.0.1.

"Target Environment" has only the defaults, "Target Platform" has everything
selected that comes by default with Eclipse, it also has the jadclipse
plugin and the tomcat plugin (but I don't think the last two make any
difference).

After updating the project from the repository (I use it in two locations,
one has Eclipse 2.0, the other has Eclipse 2.0.1) I choose "Update Classpath
..." from the context menu on the project node in the Package Explorer.

What's the difference?

Harald