Re: Override Require-Capability in Maven-Bundle-Plugin

Neil, Thanks, implementing as you suggest works. I think of it more as a 'graceful work around'! If you care to outline your solution on my SO post I'll mark as accepted. David, Once again thanks for your suggestions, much appreciated. Regards Kerry On 13/12/17 20:57, Neil Bartlett

Re: Override Require-Capability in Maven-Bundle-Plugin

From your StackOverflow post it seems that the unsatisfied requirement is this one: [caused by: Unable to resolve com.javatechnics.jpa.simple/1.0.0.SNAPSHOT: missing requirement [com.javatechnics.jpa.simple/1.0.0.SNAPSHOT] osgi.service;

Re: Override Require-Capability in Maven-Bundle-Plugin

The effective:=active clause means the requirements/capabilities are not used at runtime when wiring bundles, they are information for figuring out which bundles will work together and are used by things such as (spec) subsystems and the karaf feature installer. Aries implements the osgi jpa

Re: Override Require-Capability in Maven-Bundle-Plugin

David, Thanks for taking a look. As you and Neil Bartlett have said, my work around isn't the correct solution and I perhaps have to accept that I cannot achieve my desired result. I think this is because in part persistence units  don't have OSGi in mind so don't place nice with it? I'm