Hi Madhan, I think this is a sensible move. I like the fact you have told the dev list so they can raise an concerns with this approach. I notice the reason for us needing to go to Java 8 was due to a Jetty library upgrade- which has just been reverted. I moved up to java 8 and the latest build fails for me with: Failed tests: KafkaNotificationTest.setup:48 » Atlas Failed to start embedded kafka I did not have this issue at java 7. Any thoughts? I guess I could go back to JAVA 7, which may now work, but we are saying will not be supported.
I also notice the build has been broken for a few days now, is it realistic to expect a clean local build at the moment? all the best, David. From: Madhan Neethiraj <[email protected]> To: <[email protected]> Date: 04/10/2017 00:10 Subject: [ANNOUNCE] Java 8 as minimum requirement for Apache Atlas 1.0.0 (master) All, Atlas 1.0.0 (from master branch) will be replacing use of Titan with JanusGraph, as Titan is not being actively maintained/enhanced, while JanusGraph is. Also, this branch will be using newer version of Hadoop (3.0) and HBase (2.0). All these updates require Java 8 and won’t work in earlier version of Java. And recent change to use newer version of Jetty (ATLAS-2089) also requires use of Java 8. Given above, Apache Atlas (from master branch) would require Java 8 from now on. Apache Atlas from branch-0.8 will continue to use Java 7, as there is no plan currently to move to JanusGraph/Hadoop-3/.. in this branch. Madhan Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
