I'll stick to 3.0.2 on 3.1.x, and when master has it's OSGi versions in order, off to 4.
Meanwhile, I have a test case of mine which seems to work great with the code I was about to commit. But when I put, essentially, the same test case into the existing itest, and run with Karaf 3, I am back to Caused by: javax.el.ELException: Provider com.sun.el.ExpressionFactoryImpl not found at javax.el.FactoryFinder.newInstance(FactoryFinder.java:101)[49:javax.el-api:3.0.0] at javax.el.FactoryFinder.find(FactoryFinder.java:197)[49:javax.el-api:3.0.0] at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:197)[49:javax.el-api:3.0.0] at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:168)[49:javax.el-api:3.0.0] at org.hibernate.validator.internal.engine.messageinterpolation.InterpolationTerm.<clinit>(InterpolationTerm.java:60) On Fri, Dec 11, 2015 at 3:37 PM, Daniel Kulp <[email protected]> wrote: > >> On Dec 11, 2015, at 1:13 PM, Benson Margulies <[email protected]> wrote: >> >> I propose to add some Karaf integration tests under osgi/karaf/itests. >> >> I will code them for Karaf 4 unless someone expresses deep sadness at >> this prospect. >> >> I will do this work on the 3.1.x branch and merge it to master, since >> the OSGi versions appear to be in an odd state on master. > > There are some tests already (not many) in osgi/itests that are using Karaf > 3.0.2. That said, moving to Karaf 4 makes a ton of sense, definitely for > master. > > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >
