On Tue, Apr 25, 2017 at 2:02 PM, Carsten Ziegeler <cziege...@apache.org> wrote: > The problem might be that the framework implementation you use does not > support Java 8, e.g. if you're using an older implementation.
Which (at least in the case of Felix), basically just means that it doesn't have the required config.properties. So, if that is the case you could either update to a newer version of Felix or try to use the java.ee and package related properties of a newer felix version. regards, Karl > Regards > Carsten > > David Bosschaert wrote >> Hi Mic, >> >> The osgi.ee capabilities are exposed by newer versions of Java if they were >> compatible. So frameworks running under Java 7, Java 8 (and hopefully Java >> 9) will also expose the JavaSE capability version 1.6. >> >> More background on this versioning concept which is applied to OSGi >> 'Portable Contracts' as well here: >> https://www.osgi.org/portable-java-contract-definitions/ >> >> Best regards, >> >> David >> >> On 25 April 2017 at 12:38, Mic <zerocoo...@web.de> wrote: >> >>> Hi guys, >>> >>> i try to run org.apache.sling.commons.scheduler OSGi Bundle-Version: >>> 2.4.14 >>> under Java 8. >>> I got problems due the Bundle-RequiredExecutionEnvironment: JavaSE-1.6 / >>> Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.6))" >>> >>> There was no problem under Java 7. >>> >>> Any ideas why? >>> >>> Thanks a lot. >>> >>> Best Regards, >>> Mic >>> >>> >>> >>> -- >>> View this message in context: http://apache-sling.73963.n3. >>> nabble.com/org-apache-sling-commons-scheduler-under-Java-8-tp4072921.html >>> Sent from the Sling - Users mailing list archive at Nabble.com. >>> >> > > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org -- Karl Pauls karlpa...@gmail.com
