Eclipse Community Forums: Rich Client Platform (RCP) » Classpath problem when exporting RCP app

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » Classpath problem when exporting RCP app

Show: Today's Messages :: Show Polls :: Message Navigator

Classpath problem when exporting RCP app [message #437994]

Tue, 11 October 2005 09:20

Martin

Messages: 35
Registered: July 2009

Member

Hi,

my RCP app consists of a functionality plug-in and an
application-launching plug-in. The former depends on an external .jar
file I added to the project's Java Build Path. Now I want to export the
application as an eclipse product. I added the .jar to Extra Classpath
Entries in plugin.xml and had to remove it from the Java Build Path
(double referencing -> build error). Now I can export my product without
errors, but the .jar is not exported to the .zip file; so when my code
uses a class from the .jar a NoClassDefError is thrown. The same happens
when I run the app from within eclipse with the launch config that used
to work prior to the changes described above.

I guess I've done something wrong, added the .jar in the wrong place or
something like that. Can anyone give me advice on this?

Thanks & regards,
Martin

Report message to a moderator

Re: Classpath problem when exporting RCP app [message #437996 is a reply to message #437994]

Tue, 11 October 2005 10:01

arne anka

Messages: 133
Registered: July 2009

Senior Member

make a plugin from the jar and add it to the dependencies. how to do is
explained several times in the list-archive (www.eclipsezone.com/forums/).
basically it comes down to new -> other -> "plug-in from existing jar
archives".

Report message to a moderator

Re: Classpath problem when exporting RCP app [message #438039 is a reply to message #437996]

Tue, 11 October 2005 11:51

Martin

Messages: 35
Registered: July 2009

Member

arne anka wrote:
> make a plugin from the jar and add it to the dependencies. how to do is
> explained several times in the list-archive
> (www.eclipsezone.com/forums/). basically it comes down to new -> other
> -> "plug-in from existing jar archives".

Thanks a lot, that worked fine :) I was not aware that creating a
jar-wrapping plug-in was so easy.

Martin

Report message to a moderator