|Fun with fragments... [message #835701]
||Tue, 03 April 2012 15:09
| Daniel KrÃ¼gler
Registered: July 2009
I'm observing unexpected compile behaviour for my "home-brewed"|
bundle/fragment pair, I'm working with Eclipse 3.7.2 64-bit Classic
with an x86 JRE set.
a) I have a very simple host bundle, let's name it abc, with the
Please note that the host bundle itself has no sources, because the
complete implementation is provided by a single fragment (This is very
similar to the swt bundle). It nonetheless exports package "abc",
because that is the public API expected to be published by the fragment.
b) I have also written a corresponding fragment restricted for
win32-win32-x86, the manifest.mf is defined:
Eclipse-PlatformFilter: (& (osgi.ws=win32) (osgi.os=win32) (osgi.arch=x86))
This fragment bundle contains all the code, in particular the public API
within package abc.
If I have this bundle+fragment as a project in my Eclipse IDE,
everything is fine, which means that any depending plugins (using an
import directive), can resolve the "abc" package.
But when I set a target platform, which contains above bundle plus the
fragment and if I remove the aforementioned projects from the Eclipse
workspace, the expected package resolution does not succeed. I already
tried reloading the target-platform, cleaning the dependent projects
etc. This behaviour differs from all other (non-fragment) bundles that
are part of the target platform.
Does anyone have an idea what is going wrong here? (Let me repeat that I
have checked that the Java-runtime set matches the target platform
requirements, thus it is also an x86 JRE).
Any launcher based on the bundle+fragment starts and uses the
bundle+fragment successfully, so I'm yet not observing any runtime
problems. The real problem for me is, that all developers working at the
dependent bundles have also to ensure that they have the bundle+fragment
project in their workspace. Now, for swt a similar procedure is not
required, even though the architecture is quite similar. Is their
something wrong with any of the manifest.mf's or could that be an
I would appreciate any suggestions!
Thanks & Greetings from Bremen,
Powered by FUDForum
. Page generated in 0.04552 seconds