| [news.eclipse.platform] Re: Problems after upgrading from Eclipse 3.1 to 3.2 with external libs |
Hi Paul,
thank you, I got it!
Regards, Mirco
AFAIK this difference is an added tooling check to help cut down on the "It works in eclipse but fails when I export it" problems.
Eclipse plugins need to get info from other plugins ... i.e. in runtime if it's not in a plugin, then it's not visible*
You can use info like http://wiki.eclipse.org/index.php/Plug-in_Development_Environment to create plugins for your external jars or include them in a common library plugin.
*there are a very few exceptions to this, almost all dangerous.
Later, PW