Eclipse Community Forums: Eclipse Platform » RCP dev

Home » Eclipse Projects » Eclipse Platform » RCP dev - how to handle plugin.jars ?

RCP dev - how to handle plugin.jars ? [message #334248]

Thu, 29 January 2009 04:22

Eclipse User

Hello,

i have the following problem. We are developing an rcp application, which
uses some "common plugins". These common plugins are declared as
dependency in plugin.xml of the CORE-Plugin of our rcp-application.

During development (compile time) these works, as long as we have these
common plugins checked out as source-code in our workspace.

But now we want to switch to have only the packaged JAR-File of ever
common plugin in our workspace --> but our core plugins now doesn't find
these plugins anymore.

How must we register these Plugin-JARs in our project/-plugin.xml
settings, so that they will be found from eclipse during development time?

Re: RCP dev - how to handle plugin.jars ? [message #334253 is a reply to message #334248]

Thu, 29 January 2009 07:05

Eclipse User

Must i declare these plugins as "external plugins" (WindowsPreferences -->
Plugin-Development --> Target-Platform ?

What is the difference between workspace plugins and external plugins ?

Re: RCP dev - how to handle plugin.jars ? [message #334254 is a reply to message #334248]

Thu, 29 January 2009 09:43

Eclipse User

Originally posted by: fakemail.xyz.de

S.Schnabl schrieb:
> Hello,
>
> i have the following problem. We are developing an rcp application,
> which uses some "common plugins". These common plugins are declared as
> dependency in plugin.xml of the CORE-Plugin of our rcp-application.
>
> During development (compile time) these works, as long as we have these
> common plugins checked out as source-code in our workspace.
> But now we want to switch to have only the packaged JAR-File of ever
> common plugin in our workspace --> but our core plugins now doesn't find
> these plugins anymore.
>
> How must we register these Plugin-JARs in our project/-plugin.xml
> settings, so that they will be found from eclipse during development time?
>

If you don't want plugins for each jar and just want them to be visible
for a single project you can just put the jar file into the root folder
of the plugin.
In the plugin.xml you have to add it under Runtime -> classpath then
and don't foget to add the plugin to be exported in the buil.properties
file.

But maybe I misunderstood your problem..

Christian

Re: RCP dev - how to handle plugin.jars ? [message #334265 is a reply to message #334254]

Thu, 29 January 2009 16:02

Eclipse User

Thx for your reply, but that's not my problem. In the meantime i did some
googling and it seems, that "Target Platforms" or "Target Definition
files" are what i need...

The reason is that we try to have a little more restfully development of
our rcp application(s). Due to this we are trying to stop the direct use
of the (rapidly changing) source code of our "common plugins" in the
workspace when developing a special rcp application. Instead of we use
only stable packaged/deployable jar of such a common plugin...

Btw. "Target Platforms" seem to bring much more benefits, for example
developing your rcp-application against a special eclipse version (e.g.
3.3) in an 3.4.1 eclipse.

Previous Topic:	Filtering key binding / Activities support it someway?
Next Topic:	How to set the configuration area dynamically?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Oct 18 08:59:23 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter