Re: org.apache.sling.commons.scheduler under Java 8
Hi guys,
thanks for you help. I think i found the correct settings.
Now i use the following additional settings:
*org.osgi.framework.system.packages.extra*=${jre-1.8}
*org.osgi.framework.executionenvironment*=${ee-1.8}
ee-1.8=JavaSE-1.8,JavaSE-1.7,JavaSE-1.6,J2SE-1.5,J2SE-1.4,J2SE-1.3, \
J2SE-1.2,JRE-1.1,JRE-1.0,OSGi/Minimum-1.2,OSGi/Minimum-1.1, \
OSGi/Minimum-1.0
*org.osgi.framework.system.capabilities*=${eecap-1.8}
eecap-1.8= osgi.ee; osgi.ee="OSGi/Minimum";
version:List="1.0,1.1,1.2", \
osgi.ee; osgi.ee="JavaSE";
version:List="1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7,1.8", \
osgi.ee; osgi.ee="JavaSE/compact1"; version:List="1.8", \
osgi.ee; osgi.ee="JavaSE/compact2"; version:List="1.8", \
osgi.ee; osgi.ee="JavaSE/compact3"; version:List="1.8"
For now, the Applications starts and the Exception is gone, hope this was
the correct way (without updating to a newer Version).
Any concerns about this settings?
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-tp4072921p4072935.html
Sent from the Sling - Users mailing list archive at Nabble.com.
Re: org.apache.sling.commons.scheduler under Java 8
Hi David, thanks for the fast reply and the information. But what are my options to use the commons.scheduler under 1.8? Also the newest Version 2.5.2 which i found in the official mvn repo has the Requirement (version=1.6)), thats a little bit confuse to me. So in the Application startup process i receive the following stacktrace and the bundle is unable to start: org.apache.sling.commons.scheduler-2.4.14.jar (org.osgi.framework.BundleException: Unresolved constraint in bund le org.apache.sling.commons.scheduler [63]: Unable to resolve 63.0: missing requirement [63.0] osgi.ee; (&(osgi.ee=JavaSE)(version =1.6))) org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.sling.commons.scheduler [63]: Unable to resolve 63. 0: missing requirement [63.0] osgi.ee; (&(osgi.ee=JavaSE)(version=1.6)) at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3826) at org.apache.felix.framework.Felix.startBundle(Felix.java:1868) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191) at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295) at java.lang.Thread.run(Thread.java:745) Or is there any parameter for the sling.properties File which can help? Thanks for your help. Best Regards, Mic -- View this message in context: http://apache-sling.73963.n3.nabble.com/org-apache-sling-commons-scheduler-under-Java-8-tp4072921p4072933.html Sent from the Sling - Users mailing list archive at Nabble.com.
Re: org.apache.sling.commons.scheduler under Java 8
On Tue, Apr 25, 2017 at 2:02 PM, Carsten Ziegeler 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 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
Re: org.apache.sling.commons.scheduler under Java 8
The problem might be that the framework implementation you use does not support Java 8, e.g. if you're using an older implementation. 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 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
Re: org.apache.sling.commons.scheduler under Java 8
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 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. >
org.apache.sling.commons.scheduler under Java 8
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.
