The digest of interesting events from the world of Java, and around it # 6 (07/04/2016 - 07/17/2016)
In this issue
- JUnit 5 comes to us - Build over: CMS will be removed from Java - Java EE: Oracle breaks silence - In the wilds of JIT along with Azul … and much more
1. News
1.1.I released the first milestone release of JUnit 5
Link 1:http://www.swiftmind.com/de/2016/07/07/junit-5-0-0-m1-released/ Link 2:http://www.codeaffine.com/2016/02/18/junit-5-first-look/ ')
The developers promise a lot of nice features - support for lambdas, dynamic test registration, etc ... You can read more in the official documentation . Some of this functionality was present in previous versions. But the JUnit 4 API is far from ideal. Increasing the functionality led to the accumulation of technical debt, expressed in competing interfaces, entangled entities, and other oddities. The new version of the API will not only be more advanced, but also more convenient and complete. We wait.
That's not news. The idea to remove the CMS was materialized in the form of a JEP, and as far back as 2015. Oracle wants to focus entirely on the development of G1 . However, now the developers have come close to the beginning of cutting, which has generated a number of questions.
So, representatives of SAP and Google declare that they want to continue to develop CMS as part of their OpenJDK assemblies. Therefore, CMS can not just take and cut. It would be good to either abstract it, or turn off its compilation with some kind of macro. But even here, things are not going smoothly, since Oracle, with a big creak, is pushing the pushy from the side into the OpenJDK code base.
Oracle guys do not need all these difficulties. Ideal for them - just bang code base. Mark Reinhold's comment allows us to hope that the IT giant will show some responsibility, and the parties will be able to come to a compromise.
1.3. Trends and Trends in Java: A Great Study of RebelLabs
The guys from ZeroTurnaround conducted a large survey of Java-specialists, and made a picture of current trends in the world of Java. 75% of developers think they are better than the average for the hospital. 3 out of 5 tasted microservices to the taste, did not understand why all this is necessary. IDEA finally overtook Eclipse . And so on and so forth. Read, extremely interesting.
In short: “set aside a panic, the situation is under control, we’ll tell everything on JavaOne ”. In fact, the Java EE moaning theme is already a bit weary. Therefore, it is possible to really relax and just wait for September. And there, look, and "will resolve itself." Although it is unlikely that many of you were very tense about this :-)
Meanwhile, Mark Little from RedHat slightly clarified the situation with MicroProfile . This is an initiative about standards, and not about standards. About Java EE, and not about Java EE. It will be promoted through JCP, and not through JCP. In short, for all good, against all bad. So far, it looks too loose.
By the way, another good news - WebSphere is now Java EE 7 compliant ! Congratulations to colleagues from IBM . As they say, the road spoon for dinner.
Posh report on JIT interiors from Douglas Hawkins from Azul Systems . Highly recommended for viewing if you are not present at the event, organized by JUG.RU.
At CMS, the ground burns under your feet. Therefore, it’s time to get into the debugging of G1 problems, and figure out what it prints to the log. The author of the article rather concisely and succinctly tells how to start speaking the same language with the new garbage collector.