The problem is that your example needs an implementation of the dto
support but you installed the api bundle instead which is not suitable
for runtime.
On 20.09.2016 13:45, t...@quarendon.net wrote:
I'm really struggling to get my bundles installed in Karaf, so I'd appreciate
some hints on
Tom, if you drop them _as bundles_, karaf works like any other osgi
container -- you have to drop in all the bundles you need. You might
need to set serviceRequirements to disable in
org.apache.karaf.features.cfg if your bundle manifests are not fully
informative on the topic of service
Tom integrating karaf development and bndtools development has been tricky
but it is getting better. Karaf development is centered around Mavens
build process while bndtools is centered around a custom workspace in cnf.
This release bndtools will be supporting maven and you can see the latest
I'm not sure exactly how the "resolve" in bndtools work, but in Karaf, the
resolution
is done on all constraints, including generic capabilities / requirements,
and
including osgi services.
In this very case, you have a bundle that requires the osgi.unresolvable
capability.
Why did you add this
I'm really struggling to get my bundles installed in Karaf, so I'd appreciate
some hints on how to diagnose some issues. I'm trying to do a feature:install of
a features.xml file I've written to install my bundles.
My latest is:
missing requirement osgi.wiring.package;