I’m “ok” with building with Java8, but definitely think we need to stick with 
Java7 for runtime.   That said, I’d strongly prefer allowing building with 
Java7 as well to make sure we don’t miss issues.   I don’t see many of our 
customers moving to Java8 this year at all so maintaining Java7 compatibility 
is important to me.

Is it just a few tests that fail with Java8?   Could we create a  “Java7” 
profile that would disable the “known to fail with Java7 and we’ve investigated 
why and nothing we can do about it” tests?  A separate Jenkins job could be 
setup to run the Java7 tests compared with the Java8 to make sure we don’t miss 
things.

Dan



> On Jan 26, 2015, at 10:22 AM, Achim Nierbeck <[email protected]> wrote:
> 
> Hi,
> 
> How is everybody feeling about to switch to JDK8 for building the master
> branch? (Karaf 4)
> According to [1], Java 7 is pretty much at EOL.
> I think this needs to be addressed right now since for Pax Web 4.1. which
> is now used by Karaf 4
> it is needed to use JDK8. Not because of using any new features of Java 8
> but because of the memory issues while running the integration tests.
> There seems to be a reproducible issue since switching to Jetty 9.2 and
> running the integration tests with Java 7. Those are gone when Java 8 is
> used.
> Therefore Pax Web 4.1. uses JDK8 for building right now, though the
> switches are set to be compatible with Java 7, for source and target.
> 
> Another benefit might be to use JDK8 features already.
> 
> For me I would like to see at least JDK8 with source and target set to 7
> 
> regards, Achim
> 
> [1] - http://www.oracle.com/technetwork/java/eol-135779.html
> 
> -- 
> 
> Apache Member
> 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/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
> 
> Software Architect / Project Manager / Scrum Master

-- 
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Reply via email to