The Apache Software Foundation announced their resignation from both the JCP Executive Committee as well as the JCP as a whole. They follow recent departures such as Doug Lea in October, who said “I believe that the JCP is no longer a credible specification and standards body”, as well as more recently Tim Peierls, who voted against the Java SE JSRs.
The results of the recent Java JSRs are in, and all have passed with all but Apache voting consistently against them. Google and Tim Peierls voted against the Java SE 7 and Java SE 8 JSRs, supporting the ongoing licensing issues and field-of-use restrictions for the TCK.
Oracle has announced the umbrella JSRs for Java 7/8, covering a number of the features known from the earlier Plan B. This includes Project Coin for Java 7 and Project Lambda for Java 8, as well as specific reference to OSGi for the Java 8 modularity JSR. But it also includes fields of use restrictions for the JSR TCK. Read on to find out what's included.
In an unprecedented move, the Apache Software Foundation has announced its intention to terminate its relationship with the JCP if the rights as implementers of Java specifications are not upheld. If that's the case, they argue, then the JCP specifications are nothing more than proprietary documentation. What does this mean for the future of Java and the JCP?
The results have been announced from the unusually controversial JCP Executive Committee election, with Hologic failing to be ratified. The JCP Project Management Office will now need to choose a new candidate to replace concurrency expert Doug Lea.
Oracle and IBM have today jointly announced that IBM will collaborate in the OpenJDK community to develop the Java platform, starting with the recently revised JDK 7.
Following on from the confirmation of Plan B, with the delay to a number of JSRs and eviction of both the Lambda project as well as collection literals from Project Coin, it's interesting to take a step back and see how a change makes it into the Java environment. It's not as simple as you think.
Plan B was announced at JavaOne, which confirms that lambdas, modularity and the Swing application framework will not be part of JDK7; nor are any promises made about availability in JDK8.
In a post entitled Re-thinking JDK7, Mark Reinhold put forward a suggestion that certain previously planned elements of JDK7 be suspended until JDK8 in order to get the release out of the door sooner rather than later. What does the community think of this suggestion? Read on to find out.
InfoQ talks to Pete Muir about JBoss' Integration testing tool Arquillian, archive assembly of JARs, WARs, and EARs with ShrinkWrap, and plans for Seam 3.
Last week Adobe Systems announced it was purchasing Day Software for $240 million. The deal combines Day’s JSR-170/238 based content management and digital asset management products with Adobe’s Flex, Flash and AIR in a move to corner the web content market. In addition to being a lead company for the JSR-170/238 specifications, Day also contributes to Apache Jackrabbit and Sling.
Oracle has released version 6.9 of its popular open-source Java IDE, NetBeans. This is the first release under its stewardship since it accquired Sun Microsystems.
Effective Java author and chief Java evangelist at Google Josh Bloch gave a talk at the recent web-based Red Hat Middleware 2020 conference. The thrust of the talk was guarded optimism and concern about the future of the Java platform under Oracle's stewardship. InfoQ spoke to him to find out more about his thinking.
Stephen Colebourne, lead of the JSR 310 Date and Time API, has recently published an Early Draft Review of the proposed additions and changes to the Java language. InfoQ caught up with Stephen at QCon London to find out more about the project.
Bean Validation (JSR 303), one of the core features of Java Enterprise Edition Version 6 Release, defines a metadata model and an API for entity validation. The default metadata source is annotations, but the developers can extend it using XML descriptors. The API also provides a mechanism to add custom validation constraints as well as a way to query the constraint metadata repository.