Android O (Treble with a cause), JCP EC says No to Project Jigsaw, and Spring Boot Demo. On this episode of Java News and Code!
In this video:
- J Steven Perry, Principal Consultant, Makoto Consulting Group, Inc
Java Community Process Executive Committee Says No to JSR 367 (Project Jigsaw)
The Java Community Process Executive Committee gives project Jigsaw a thumbs down in last week’s Public Review ballot.
Project Jigsaw is the code name for JSR 367, the proposed Java Platform Module System, which promises to bring the design principle of modularity to the Java platform.
The idea is that pieces of a software system fit together like jigsaw puzzle. Get it?
In April IBM and Redhat were expressing their intention to vote No on JSR 367. With Redhat’s Scott Stark posting on April 14th some concerns about JSR 367.
The authors expressed concerns that the JSR would ultimately create a Disrupted Ecosystem, which would result in Fragmentation of the Java community.
JSR 367, the post said, was “Reinvention, Not Standardization” and the post’s authors, from Redhat, Redhat, Redhat, Redhat, Redhat and others implied that Jigsaw was designed with Java’s own self interest in mind, rather than the interests of vendors like Redhat, Redhat, Redhat, Redhat, Redhat, and others.
But Redhat and IBM weren’t the only No votes. From the vote log the 11 other No votes, the main sticking point seemed to be related to automatic names, but a few of the No voters expressed concerns over a “lack of consensus” among members of the Expert Group.
With Software AG saying in their NO vote:
“Software AG is concerned about the lack of a healthy consensus among the members of the Expert Group. Although we understand that a perfect consensus and zero outstanding issues may be unachievable, we believe that a healthier consensus is possible…”
But there were some Yes’s and among them were Azul Systems, Goldman Sachs, and Fujitsu Limited, who said this in their Yes vote:
“There are a lot of concerns, but we hope EG members will resolve them by the next ballot.”
So what’s next for JSR 367 and Java 9?
Following the No vote, the Spec Lead and Expert Group have 30 days to resolve the issues and put it to another vote.
What this does to the Java 9 release date is anybody’s guess.
This is a story we’ll be following closely for sure.
Android O: (Project) Treble With a Cause
A huge problem for device makers that support Android is upgrading existing devices to new versions of Android.
But Android O promises to ease some of that pain for device makers by introducing a few architectural changes.
An announcement on the Android Developer Blog for a new project codenamed project Treble, the new architecture provides a new Vendor interface used to insulate device makers from changes in subsequent releases of Android.
The way it works currently looks like this:
- Android puts out a new Dessert release.
- Silicon partners like chip and board makers get ahold of the
release and add any customizations they need.
- Next, device makers add their own and their carriers’ features
and other customizations.
- Finally, the release is ready to be pushed out to consumers like
you and me.
And that process can take a while to complete from start to finish.
And is particularly painful to all of Android’s vendor partners.
Project Treble promises to address that by introducing the Vendor Interface and Vendor Test Suite, or VTS. The Vendor Interface is designed to insulate the Vendor’s implementation from the rest of the Android OS framework.
Before Treble, for each new Android release, vendor partners were required to rework their implementations to ensure backward compatibility with existing devices.
With Treble, when a new release of Android comes out, the Vendor Interface insulates the changes in the new version of Android from the vendor’s implementation.
This should result in faster implementation times for vendors and fewer headaches to consumers
If you’re an Android developer, and you’d like to try out Android O, check out this page, which contains instructions on how to upgrade your device.
Code Talk-through: Spring Boot
In today’s code talkthrough, I’ll walk you through creating a simple Spring Boot application.
The code you’ll see can be downloaded from Github
SpringBoot takes an opinionated view of Spring configuration, which allows you to create applications that “just run”.
In the talk-through, I’ll show you how to:
- Clone the HelloSpringBoot code from GitHub
- Import the code into Eclipse
- Build and run the executable JAR
- Access the simple RESTful application
For a more in-depth look at Spring Boot, check out the Spring Boot Basics Tutorial I wrote for IBM developerWorks. It takes you deeper into Spring Boot concepts, and shows you how to build a simple Spring MVC application, run it, and access it through SoapUI (though any HTTP client should work fine).
Sweet as Honey by Topher Mohr and Alex Elena, YouTube Audio Library (Free to use for commercial purposes, no attribution required), see YouTube Terms of Service and this YouTube support article for details.