acoburn commented on issue #42: TAMAYA-383 Let OSGi skip thread classloader key URL: https://github.com/apache/incubator-tamaya/pull/42#issuecomment-462346384 I can confirm that, with this commit, `tamaya-core` deploys in Karaf 4.2 and the bundles are all active. ``` karaf@root()> bundle:list START LEVEL 100 , List Threshold: 50 ID │ State │ Lvl │ Version │ Name ───┼────────┼─────┼───────────────────────────────┼──────────────────────────── 21 │ Active │ 80 │ 4.2.0 │ Apache Karaf :: OSGi Servi 43 │ Active │ 80 │ 1.3.2 │ javax.annotation API 44 │ Active │ 80 │ 0.4.0.incubating-201902111420 │ Apache Tamaya - API 45 │ Active │ 80 │ 0.4.0.incubating-201902111420 │ Apache Tamaya - SPI Support 46 │ Active │ 80 │ 0.4.0.incubating-201902111420 │ Apache Tamaya - Core ``` I do still see errors in the log such as: java.lang.ClassNotFoundException: org.apache.tamaya.core.internal.DefaultConfiguration not found by org.apache.tamaya.core and java.lang.ClassNotFoundException: org.apache.tamaya.core.internal.CoreConfigurationContextBuilder not found by org.apache.tamaya.core and java.lang.ClassNotFoundException: org.apache.tamaya.core.internal.ConfigValueEvaluator not found by org.apache.tamaya.core But perhaps those changes are part of #41 (TAMAYA-381) -- they are just due to the `META-INF/services` values pointing to the wrong class names. Should both of those commits be merged to see the correct behavior?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
