3 ms·
> The biggest problem I've found so far is simply 3rd party dependencies that aren't packaged with OSGI manifest information. It's a mess, and I fear Java 9/10
by _pmf_ 10y ago
> The biggest problem I've found so far is simply 3rd party dependencies that aren't packaged with OSGI manifest information.
It's a mess, and I fear Java 9/10's modularization approach will even make it worse (so that instead of P2 (Eclipse's Equinox' OSGi bundles) and Maven, we'll have another set ... sigh. I'm still looking for a solution that transparently translates Maven metainformation to OSGi bundle information at some higher level (for example by hooking into the OSGi container's dependency resolution logic).
Edit: apparently, such a mechanism exists (ResolverHook)
- sytringy05 10y agoisn't that exactly what wrap is for?
- mindcrime 10y agoThat has mostly worked well for me when dealing with non-OSGI jars. Once I figured out how to set things up using the features.xml file and specify wrap: for the generic jars, things worked nicely. All of this said, I'm fairly new to OSGI, so I may still run into some dark corners that will turn me off. But right now, it seems to be serving the purpose well.