Hi, I guess it happens only with JDK14 (as Karaf is running fine on Jenkins using JDK11). It’s really important to mention the environment to qualify the issue.
A possible cause is the content of etc/jre.properties (for JRE14) is not correctly loaded. In etc/config.properties, we load the jre.properties based on ${jre-${java.specification.version}}. Let me check the java.specification.version returned by JDK14 (maybe it’s not just 14 but 14-something for instance). Regards JB > Le 2 nov. 2020 à 01:48, Leschke, Scott <slesc...@medline.com> a écrit : > > Karaf 4.3.0 on Windows, JDK 14. All java.* packages, including java.lang, > show as Unsatisfied Requriements in bundle:diag output. Setting > karaf.framework=equinox > yields similar results. > > org.osgi.framework.BundleException: Unable to resolve > medline.bam.provider.jdbc [181](R 181.0): missing requirement > [medline.bam.provider.jdbc [181](R 181.0)] osgi.wiring.package; > (&(osgi.wiring.package=com.medline.osgi)(version>=1.0.0)(!(version>=2.0.0))) > [caused by: Unable to resolve medline.osgi [169](R 169.0): missing > requirement [medline.osgi [169](R 169.0)] osgi.wiring.package; > (&(osgi.wiring.package=com.medline.util.service)(version>=1.0.0)(!(version>=2.0.0))) > [caused by: Unable to resolve medline.util [163](R 163.0): missing > requirement [medline.util [163](R 163.0)] osgi.wiring.package; > (osgi.wiring.package=java.io <http://java.io/>)]] Unresolved requirements: > [[medline.bam.provider.jdbc [181](R 181.0)] osgi.wiring.package; > (&(osgi.wiring.package=com.medline.osgi)(version>=1.0.0)(!(version>=2.0.0)))] > at > org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368) ~[?:?] > at > org.apache.felix.framework.Felix.startBundle(Felix.java:2281) ~[?:?] > …. > > Scott