[news.eclipse.platform] Re: Plug-in problem with jars

["Walter Harley" <wharley@xxxxxxx>]

"Michael Pisula" <pisula@xxxxxxxxxxxxxxxxx> wrote in message 
news:58a96e814b475ac100ac2137fb902d78$1@xxxxxxxxxxxxxxxxxx
> > We tried moving all jars to a plug-in which all other plug-ins depend 
> > on,
> and assumed that the other plug-ins would import the jar via the plug-in. 
> This did not work. Manually adding the jars to each plug-ins build path 
> only solved the problem partially, because then we faced "Access 
> restriction" problems.

Putting your jars into shared plug-ins is the correct approach.  It sounds 
like you just didn't get that working quite right.  In addition to putting 
the jars on the bundle classpath, you also need to export the packages 
contained by the jar, again in the manifest classpath.

The PDE manifest editor should do these things for you, if you let it.

Is the problem that you need a way to automatically update the manifest.mf 
if the contents of the jar change?  I imagine it might be possible to 
automate that, but I think most people just handle it manually.