Eclipse Community Forums: Eclipse Platform » exporting classes : plugin manifest versus java build tab

Home » Eclipse Projects » Eclipse Platform » exporting classes : plugin manifest versus java build tab

exporting classes : plugin manifest versus java build tab [message #286664]

Tue, 14 June 2005 10:02

Eclipse User

Hi,

Maybe I'm just overlooking the right way to do this but I don't really get
why when I want to export a jar file or a set of classes from my plugin
project I need to define it in 2 different locations. I have to add it to
the runtime tab of the plugin manifest for the plugins to function
correctly when running and I have to add it to the Java builders "order
and export" tab to have it function when writing code.

Now this strikes me as particulary odd since it seems to leave a hole for
developers to type code with classes not available at runtime and thus
crashing with noClassDefFoundErrors.

It also seems odd as project dependencies can be defined as project
references, java build path dependencies and plugin dependencies. And is
an error to do this at multiple places, defining it in plugin.xml is
enough for development environment.

Anyone any thoughts on this ?

With kind regards,
Erik Vanherck

Re: exporting classes : plugin manifest versus java build tab [message #286668 is a reply to message #286664]

Tue, 14 June 2005 11:05

Eclipse User

Originally posted by: Lamont_Gilbert.rigidsoftware.com

Erik Vanherck wrote:
> Hi,
> Maybe I'm just overlooking the right way to do this but I don't really
> get why when I want to export a jar file or a set of classes from my
> plugin project I need to define it in 2 different locations. I have to
> add it to the runtime tab of the plugin manifest for the plugins to
> function correctly when running and I have to add it to the Java
> builders "order and export" tab to have it function when writing code.
> Now this strikes me as particulary odd since it seems to leave a hole
> for developers to type code with classes not available at runtime and
> thus crashing with noClassDefFoundErrors.
> It also seems odd as project dependencies can be defined as project
> references, java build path dependencies and plugin dependencies. And is
> an error to do this at multiple places, defining it in plugin.xml is
> enough for development environment.
>
> Anyone any thoughts on this ?
> With kind regards, Erik Vanherck
>

I only add to my manifest or plugin.xml file. I dont use the projects
build tab for plugin projects in general. I dont have anything special
in my project properties, its all in the manifest. Maybe you made some
mistake.

CL

Re: exporting classes : plugin manifest versus java build tab [message #286699 is a reply to message #286668]

Wed, 15 June 2005 07:18

Eclipse User

Could be of course,

I create a new plugin project A, which is a simple empty plugin. I copy a
jar file in the project (in this case ibm's jt400 jar for the iseries
toolbox but it doesn't matter). I add to the manifest that I want to
export com.ibm.access which is included in the jar file and it it to the
plugin classpath. It then displays an problem that com.ibm.access is not
inside the project. So I add the jar file to the libraries tab of the java
build path of the project properties and the errors are solved.

After this I create a new plugin project B that has a dependency on
project A. If I don't export using the java build properties the jt400 jar
file from plugin project A then the source code in plugin project B does
not recognize the classes and will not compile.

But this does not prevent me from using classes that may not be available
at runtime as my plugin manifest can be different and has a limit on the
packages exported while the java build path does not.

Previous Topic:	How to save in a multipage form editor?
Next Topic:	Extend/change problem view

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 02:21:28 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter