| Unable to see some wrapped plugin from the target platform [message #22876] |
Sun, 21 September 2008 13:28  |
Eclipse User |
|
|
|
Hi all,
I've been struggling in the past days to define a target platform for our
rcp development.
For some of or core plugins or to use some opensource libraries, we've
been used to wrap them in a plugin. (Say create a specific plugin that
will basically just contain a lib directory with the wrapped jar, and a
MANIFEST.MF that will Export the necessary packages.
Those wrapper were designed using Eclipse 3.2. The thing I'm now trying to
do is to create a 3.2 Target using a 3.4 development environment. In fact,
until now, we've been developing RCP without TP (yes, we know it's bad,
that's why I'm working on now).
The thing is: even if PDE (in window/Preferences) seems to detect
correctly those wrapped bundle, but is totally unable to see what's
inside. It's as if only the MANIFEST.MF could be read :-/.
Other thing: those wrapped jars come from the exported product we made,
which is working. So I guess they're correct. At least for Eclipse 3.2.
So my question is quite simple:
* Is there any known difference between 3.2 and 3.4 PDE plugin recognition?
* Or, is there some tolerance in the bundle structure that'd no more be
allowed?
* Here are some of those wrapped plugins : http://ehehe.free.fr/osgi/ If
you see something that's clearly bad, or could cause problem. Please point
them.
So far, the only way I found to work this around was to directly modify
the MANIFEST of those plugins and stop wrapping them. The thing is I read
that OSGi spec allow to wrap jar, so I can't see why it doesn't work.
I wanted to post here before considering filing an issue in the Bugzilla.
Thanks a lot. Thanks for reading :).
|
|
|
|
| Re: Unable to see some wrapped plugin from the target platform [message #23009 is a reply to message #22922] |
Mon, 22 September 2008 12:57  |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Baptiste MATHUS schrieb:
> Well, it seems like it was finally really simple...
> There is a bug in the JDT
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=147831. In fact, this is
> confirmed to be supported with Equinox (as it's OSGi compliant), but has
> never been supported by the Java Compiler (Eclipse or javac).
>
> So, here's a small advice if you plan to setup a target platform and
> have some wrapped jars. Use the "unzip" strategy instead of wrapping the
> jar in the bundle. It will save you some headaches :-).
>
> Cheers.
>
but its not always your own bundle, where you can decide how to bundle
it. in some 3rdparty bundles it helps to import binary into workspace
and then in MANIFEST.MF go to Runtime tab and add "." to classpath. then
your compiler is happy and because equinox can handle this in your
launcher config you can use the original from target platform
ekke
|
|
|
|
| Re: Unable to see some wrapped plugin from the target platform [message #580889 is a reply to message #22922] |
Mon, 22 September 2008 12:57 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Baptiste MATHUS schrieb:
> Well, it seems like it was finally really simple...
> There is a bug in the JDT
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=147831 In fact, this is
> confirmed to be supported with Equinox (as it's OSGi compliant), but has
> never been supported by the Java Compiler (Eclipse or javac).
>
> So, here's a small advice if you plan to setup a target platform and
> have some wrapped jars. Use the "unzip" strategy instead of wrapping the
> jar in the bundle. It will save you some headaches :-).
>
> Cheers.
>
but its not always your own bundle, where you can decide how to bundle
it. in some 3rdparty bundles it helps to import binary into workspace
and then in MANIFEST.MF go to Runtime tab and add "." to classpath. then
your compiler is happy and because equinox can handle this in your
launcher config you can use the original from target platform
ekke
|
|
|
Powered by
FUDForum. Page generated in 0.03651 seconds
Home