Eclipse Community Forums: Eclipse Platform » Problems after upgrading from Eclipse 3.1 to 3.2 with external libs

Home » Eclipse Projects » Eclipse Platform » Problems after upgrading from Eclipse 3.1 to 3.2 with external libs

Problems after upgrading from Eclipse 3.1 to 3.2 with external libs [message #310287]

Tue, 28 November 2006 07:45

Eclipse User

Originally posted by: eclipse.mirco-dunker.de

Hi,

I have an Eclipse Plugin-Project that uses external lib's witch are
added to the build path. When I run this Plugin as an Eclipse
Application under Eclipse 3.1 everything works fine but under Eclipse
3.2 the same Project throws a "java.lang.NoClassDefFoundError" Exception
when the part containing the extern lib. is called. It seems that the
lib. wasn't found.

Are there any changes between 3.1 and 3.2 containing the classpath
management? Or could someone give me some hint?

Regards,
Mirco

Re: Problems after upgrading from Eclipse 3.1 to 3.2 with external libs [message #310292 is a reply to message #310287]

Tue, 28 November 2006 08:31

Eclipse User

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_Enviro nment 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

Re: Problems after upgrading from Eclipse 3.1 to 3.2 with external libs [message #310307 is a reply to message #310292]

Tue, 28 November 2006 11:09

Eclipse User

Originally posted by: eclipse.mirco-dunker.de

Hi Paul,

thank you, I got it!

Regards,
Mirco

Paul Webster wrote:
> 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_Enviro nment 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

Previous Topic:	[Activities] failure when in separate plug-in
Next Topic:	Establishing Initial Launch Configurations

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 18 07:33:50 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter