OK but in this case it's actually pax-jdbc-config that is providing/registering the service and the feature that I am defining that requires the service. Are you proposing that I workaround this problem by having the feature that requires the service also declare that it provides it as a capability?
-- View this message in context: http://karaf.922171.n3.nabble.com/Features-Core-bundle-stuck-in-Resolved-state-tp4047964p4048056.html Sent from the Karaf - User mailing list archive at Nabble.com.
