Hi Martin That capability (matching the service requirement) is provided by junit-jupiter-engine, which itself has a similar requirement on junit-platform-launcher. Adding both should do it:
<bundle>mvn:org.junit.jupiter/junit-jupiter-engine/5.14.4</bundle> <bundle>mvn:org.junit.platform/junit-platform-launcher/1.14.4</bundle> You're right that the framework resolver ignores effective:=active requirements. However the Karaf features resolver doesn't: it only skips osgi.service requirements (when serviceRequirements=disable) and treats everything else as mandatory, whatever the effective directive says. If you'd rather not install the engine and launcher, you can declare the capability on your feature instead: <capability>org.junit.platform.engine;org.junit.platform.engine=junit-jupiter;version:Version=5.14.4</capability> Regards JB On Tue, Oct 6, 2026 at 2:40 PM Lichtin, Martin via user < [email protected]> wrote: > As part of venturing into opentelemetry tracing and the ability to test > it, I'm looking at extending a Pax-Test to include InMemorySpanExporter. > > This requires an ever-longer list of bundles to satisfy all the imports.. > > <bundle>mvn:org.opentest4j/opentest4j/1.3.0</bundle> > <bundle>mvn:org.junit.platform/junit-platform-engine/1.14.4</bundle> > <bundle>mvn:org.junit.platform/junit-platform-commons/1.14.4</bundle> > <bundle>mvn:org.junit.jupiter/junit-jupiter-api/5.14.4</bundle> > <bundle>mvn:org.assertj/assertj-core/3.27.7</bundle> > <bundle>mvn:net.bytebuddy/byte-buddy/1.18.14</bundle> > <bundle>mvn:io.opentelemetry/opentelemetry-sdk/1.66.0</bundle> > <bundle>mvn:io.opentelemetry/opentelemetry-sdk-metrics/1.66.0</bundle> > <bundle>mvn:io.opentelemetry/opentelemetry-sdk-logs/1.66.0</bundle> > <bundle>mvn:io.opentelemetry/opentelemetry-sdk-common/1.66.0</bundle> > <bundle>mvn:io.opentelemetry/opentelemetry-sdk-trace/1.66.0</bundle> > <bundle>mvn:io.opentelemetry/opentelemetry-sdk-testing/1.66.0</bundle> > > I'm finally stuck at the following missing capability: > > Unable to resolve junit-jupiter-api/5.14.4: > missing requirement [junit-jupiter-api/5.14.4] > org.junit.platform.engine; > > filter:="(&(org.junit.platform.engine=junit-jupiter)(version>=5.14.4)(!(version>=6)))";effective:=active > > Would anyone know where this is provided? > > I found one mention at > https://github.com/eclipse-tycho/tycho/issues/5448 which indicates the > Felix resolver should not even fail at this point... > > Any suggestions appreciated > > - Martin > > >
