> This has leaded to an unstable version of Eclipse Europa to be added
> to our tree.
What's unstable about it?
It's not unstable in the way you understood it, it's just that it's not yet marked stable as per Gentoo stabilization process. Some bugs such as the one I am working on right now needs fixing before it can be labeled stable.
I'm not a newsgroup guy myself. Looking at your post, have you
considered working with the Orbit project to keep these third-party
libraries updated at eclipse.org?
As for the issue you're seeing, it's complicated and I don't fully
understand it myself. How did you "fiddle with the manifest in the
Junit 4 bundle to include a dependency to our local system hamcrest
jar"?
I added an Import-Package directive.
Things are extracted to your OSGi bundle cache (the 34/1/.cp
directory) when the bundles are initialized. I'm not sure why this
particular JAR is being extracted, though.
Yes, I dont know why it happens - it does not happen with for example icu4j, which is another one of our system jars that I symlinked to in the Eclipse plugin folder.
Perhaps it's the way you
added it to the MANIFEST.MF of the bundle. Does the hamcrest JAR you
have on your system have OSGi metadata in it? If so, couldn't you just
add it as a bundle and make the junit4 bundle "Require-bundle" or
"Import-package" it?
yes, the hamcrest jar has meta data in it.
We (Fedora) run the Equinox FileInitializer application to
pre-initialize our system-wide arch-specific directory
(/usr/lib{,64}/eclipse in this case) with shared libraries (.sos). If
the above doesn't work, you could try doing that with the .jar file in
this case.
I am not sure the issue is related to native shared libraries. I am pretty sure it's an OSGi problem / jar problem.
What contacts do you have upstream that could help me with this?
Jean-Noel
