| Trouble with o.e.e.launcher companion library: "Eclipse-BundleShape: dir" ignored? [message #516872] |
Thu, 25 February 2010 12:22  |
 Yang Meyer
Messages: 7
Registered: July 2009 |
Junior Member |
|
|
Hi,
I am trying to make a product out of the example application included
with Riena. There is already a .product configuration file. So in the
Overview tab of that file, in the section "Exporting" I click "Eclipse
Product export wizard" to make the .exe file etc for my machine (Vista
32bit).
This turns out a directory containing (among others) the .exe file and a
plugins directory. In this plugins directory, the companion library for
the o.e.equinox.launcher , i.e. o.e.equinox.launcher.win32.win32_x86,
appears as a JAR. Peeking into the Manifest contained therein shows that
it specifies: "Eclipse-BundleShape: dir" -- which I understand to mean
that the fragment should have been unpacked into a folder. (This is my
understanding based on
http://eclipsesource.com/blogs/2009/01/20/tip-eclipse-bundle shape/ and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=157562 --
Please correct me if I'm wrong.)
And since the launcher requires the platform-specific fragment to be in
the shape of a directory
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=176084#c1 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=195947#c3), the launcher
duly complains about not being able find the companion shared library.
Replacing the fragment JAR with the corresponding directory (copied
locally from my SDK installation's plugins directory) "fixes" the
problem and I can launch my app. However it would be "nice", to say the
least, if we didn't have to do this fix manually after every product export!
I'm afraid my knowledge of what exactly happens in the (PDE?) build is
very deep... yet. Based on what I have learned, here are some questions
that perhaps you could answer to point me in the right direction:
* Who declares the "Eclipse-BundleShape: dir" for the fragment? (Where?)
* Why is the fragment JARed despite the "Eclipse-BundleShape: dir" in
the manifest?
* Would I ever need to tell PDE to unpack the o.e.e.launcher.win32...
fragment - why does it not "know" that the platform-specific companion
libraries need to be unpacked? If yes, how can I do it?
* Where exactly does my product's .exe file come from? Is my current
SDK's eclipse.exe simply copied to the new product?
Thanks, and best regards,
Yang
|
|
|
|
| Re: Trouble with o.e.e.launcher companion library: "Eclipse-BundleShape: dir" ignored? [message #516922 is a reply to message #516872] |
Thu, 25 February 2010 09:22  |
|
Hello, I think that the answer can be found in the comments below Chris' post. Indeed, you probably use a feature, with the unpack attribute set to false. In that case (bundles in a feature + unpack specified to false), the Eclipse-BundleShape is not used.
If you have a feature, try to set the unpack value to true for your bundle.
Yang Meyer a écrit :
> * Who declares the "Eclipse-BundleShape: dir" for the fragment? (Where?)
The MANIFEST.MF of the fragment.
> * Why is the fragment JARed despite the "Eclipse-BundleShape: dir" in
> the manifest?
Probably because of an unpack="false"
> * Would I ever need to tell PDE to unpack the o.e.e.launcher.win32...
> fragment - why does it not "know" that the platform-specific companion
> libraries need to be unpacked? If yes, how can I do it?
No, properties are correctly set in launchers bundles and feature.
> * Where exactly does my product's .exe file come from? Is my current
> SDK's eclipse.exe simply copied to the new product?
I think it comes from the launcher, or from PDE-build.
--
Mickael Istria - BonitaSoft S.A.
http://www.bonitasoft.com/products/downloads.php
|
|
|
| Re: Trouble with o.e.e.launcher companion library: "Eclipse-BundleShape: dir" ignored? [message #517123 is a reply to message #516922] |
Fri, 26 February 2010 10:53 |
Yang Meyer
Messages: 7
Registered: July 2009 |
Junior Member |
|
|
Am 25.02.2010 15:10, schrieb Mickael Istria:
> Hello, I think that the answer can be found in the comments below Chris'
> post. Indeed, you probably use a feature, with the unpack attribute set
> to false. In that case (bundles in a feature + unpack specified to
> false), the Eclipse-BundleShape is not used.
Thanks for your quick and helpful reply. I will look into this. Starting
from a clean slate (new SDK, new Workspace, freshly checked-out
projects) the product export indeed unpacks the launcher companion
library. So you're probably right, there must be a feature + unpack
somewhere lingering on.
Cheers,
Yang
|
|
|
Powered by
FUDForum. Page generated in 0.03953 seconds
] 
Search
Help
Register
Login
Home
