Capabalities are evaluated in both directions. That works fine in my environment.
A Feature example with capability could look like this: Did you try to add the log dependency as in above example? Can you post your feature definition? Mike David Daniel wrote > I think I have figured out where I was going wrong. If I include > framework > as a prerequisite then it gives me an error message that I believe is more > accurate. > > [ERROR] Failed to execute goal > org.apache.karaf.tooling:karaf-maven-plugin:4.0.4:assembly > (default-assembly) on project server-installer: Unable to build assembly: > Unable to resolve root: missing requirement [root] osgi.identity; > osgi.identity=aardvarkconfigurerbundles; type=karaf.feature; version=0; > filter:="(&(osgi.identity=aardvarkconfigurerbundles)(type=karaf.feature)(version>=0.0.0))" > [caused by: Unable to resolve aardvarkconfigurerbundles/1.0.0: missing > requirement [aardvarkconfigurerbundles/1.0.0] osgi.identity; > osgi.identity=osgi.enroute.configurer.simple.provider; type=osgi.bundle; > version="[1.2.2.201509211431,1.2.2.201509211431]"; resolution:=mandatory > [caused by: Unable to resolve > osgi.enroute.configurer.simple.provider/1.2.2.201509211431: missing > requirement [osgi.enroute.configurer.simple.provider/1.2.2.201509211431] > osgi.service; filter:="(objectClass=org.osgi.service.log.LogService)"; > effective:=active]] -> [Help 1] > > I am using the 1.3.0 version of features and that has the ability to add > requirements and capabilities. > http://karaf.apache.org/manual/latest/users-guide/provisioning-schema.html > I am wondering if the veriffier is taking the requirements out of the > bundles but is not taking the capabilities out of the bundles. I was > hoping that if I put a dummy frameworkcapabilities feature in that just > specified that it has the capabilities that the verifier feels it is > missing then I might be ok. Does anyone have a framework 1.3.0 sample > with > requirements and capabilities. > > On Tue, Mar 1, 2016 at 6:39 AM, Mike Rumpf < > mikey99@ > > wrote: > >> The correct way is to work with feature dependencies, e.g. >> >> >> >> (in the \src\main\feature\feature.xml) >> >> Than the resolver will be able to resolve the missing dependencies. >> However >> from my experience setting the *prerequisite* property to *true *will >> lead >> to various build errors. (Don't know if you did that though). >> >> You also might need to use Maven-Excludes in your feature-pom to avoid >> some >> dependency-pitfalls. >> >> If you add your features to the boot-features in the assembly they won't >> be >> verified (contrary to being listed under startup features). Avoid >> non-osgi >> bundles in your features. (This would lead to the wrap feature being >> verified and the build will fail because of missing >> log-implementation...) >> >> The Karaf-Maven-Plugin is quite tricky to configure right. >> >> Hope that helps, >> Mike >> >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Issue-building-with-karaf-maven-plugin-tp4045602p4045642.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> -- View this message in context: http://karaf.922171.n3.nabble.com/Issue-building-with-karaf-maven-plugin-tp4045602p4045649.html Sent from the Karaf - User mailing list archive at Nabble.com.
