[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.platform] Re: should .classpath be bundled with deployable plugins?

You typically don't even need to do the PDE update classpath. Just use the plugin/manifest editor and add the plugin on the Dependencies page and the classpath will automatically be updated. That is because it uses the Plugin Dependencies container in the classpath, and this guy automatically updates himself when the manifest is changed.

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

-- Thanks, Rich Kulp