These are chat archives for OfficeDev/ews-java-api

21st
Jan 2015
Asbjørn Aarrestad
@ahaarrestad
Jan 21 2015 05:46
@evpaassen Java 1.6 does not backfire. we have to work withing the given environment, and that is just a challenge. I'm just a bit surprised we did not see this during testing, but perhaps ci is running java 8 in java 6 compliance mode? thus not detecting the problem?
Erik van Paassen
@evpaassen
Jan 21 2015 09:25
CI is running with JDK7, currently. The project is compiled against the 1.6 language level though, but this isn't a compile error obviously.
Asbjørn Aarrestad
@ahaarrestad
Jan 21 2015 10:14
@evpaassen missing some junit-tests?
Erik van Paassen
@evpaassen
Jan 21 2015 10:23
@ahaarrestad No? The tests would fail on Java 6, but no one ran the tests against Java 6.
Asbjørn Aarrestad
@ahaarrestad
Jan 21 2015 10:57
@evpaassen Can we ask ci to jun jdk6?
Erik van Paassen
@evpaassen
Jan 21 2015 10:59
@ahaarrestad No, Travis CI does not support Oracle JDK6: http://docs.travis-ci.com/user/languages/java/
Asbjørn Aarrestad
@ahaarrestad
Jan 21 2015 11:02
@evpaassen just read that page. Don't know If I agree to the argument, though.... Will we get the same effect using openJDK6 ?
Erik van Paassen
@evpaassen
Jan 21 2015 11:07
If you'd assume OpenJDK6 behaves exactly the same as Oracle JDK6. But most likely, it will not. Testing with OpenJDK6 tests compatibility with OpenJDK6, as testing with Oracle JDK6 would tell you something about compatibility with Oracle JDK6.
Asbjørn Aarrestad
@ahaarrestad
Jan 21 2015 11:08
I agree. that's why I don't agree with the argument in the travis-ci docs.
you may want to move on, but you can't
Erik van Paassen
@evpaassen
Jan 21 2015 11:11
Java 7 will become EOL too in April (http://www.oracle.com/technetwork/java/eol-135779.html), so we'll have to keep an eye on Travis JDK support.
Asbjørn Aarrestad
@ahaarrestad
Jan 21 2015 11:14
that site states that oracle is supporting (for paying customers) jdk 6 until 2018.....
Mike Noordermeer
@MikeN123
Jan 21 2015 11:32
Yeah, so unless Microsoft is going to pay to provide all contributors with an SDK, we can consider it EOL.
It should be fine to test against OpenJDK6 though, apart from some crypto differences it should be the same.
Erik van Paassen
@evpaassen
Jan 21 2015 11:32
should