[news.eclipse.platform] Re: should .classpath be bundled with deployable

[AL <unbonnevie@xxxxxxxxx>]

Sorry...I failed to mentioned that the plugin that depends on jar files 
from other plugins is OSGI bundled, that is, with a manifest file. 
Whereas, the plugins that have the jar files are not OSGI bundled, that 
is, no manifest file.  These plugins are tailored with the plugin.xml in 
the fashion of Eclipse 3.0.0.

Thanks.

Paul News wrote:

> Actually, when it's deployed it is the manifest that determines who can 
> see what.
>
> a plugin declares it's internal classpath and what packages it exports. 
>  Another plugin just needs to say it depends on the first plugin.
>
> If you have multiple jars in a plugin, the correct order of operations 
> is to update the manifest so the Bundle-Classpath is correct within that 
> plugin, and then go to the project popup men>PDE Tools and update 
> classpath.  The .classpath is used for compiling and running within 
> eclipse.
>
> Later,
> PW