Just one more data point... we are using Karaf 2.2.4 on top of JDK7, with sources compiled using JDK7 without any problem so far.
Regards, Raman Principal VIVO Systems On 03/28/2012 03:58 PM, Andreas Pieber wrote: > In detail this depends on the details of your setup. Nevertheless, in > general (a) start karaf 2.2.x using jre 7 works; (b) compiling your > bundles using target lvl jre < 7 in the maven compiler plugin and > running it on karaf 2.2.x using jdk 7 works too. That's what I do at > my environments. I've not tested if it works in other combinations > too, but I assume so. Best to simply give it a try and report your > experiences :-) > > Kind regards, > Andreas > > On Wed, Mar 28, 2012 at 17:18, Achim Nierbeck <[email protected]> wrote: >> well if you rebuild your service with JDK7 you surely need to >> configure Karaf to also use the required JDK/JRE otherwise it won't >> start at all. >> Though I'm unsure if Karaf 2.2.5 does run with JDK7, afaik only Karaf >> 3.0.0 was tested with JDK7. >> Another possibility is to compile your service with jdk7 and target >> run-time set to java 6. >> >> regards, Achim >> >> 2012/3/28 James Gartner <[email protected]>: >>> Right now I'm using 2.2.5, and basically we want to try to recompile a >>> current 1.6 service bundle using JDK 1.7, and then redeploy -- we are not >>> currently taking advantage of any of the 1.7 changes at all or special >>> packages. >>> Just not sure how the 1.7 dependencies would be resolved -- do we just need >>> to repoint JAVA_HOME on the Karaf machine to Java 7 JDK (or do we even need >>> to do that at all?) >>> >>> -- >>> View this message in context: >>> http://karaf.922171.n3.nabble.com/Bundles-built-with-JDK-7-tp3864379p3864742.html >>> Sent from the Karaf - User mailing list archive at Nabble.com. >> >> >> >> -- >> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> >> Committer & Project Lead >> blog <http://notizblog.nierbeck.de/>
