Angular shitstorm: What's your opinion on the controversial plans for Angular 2.0?
Break the walls down

JBoss open up commercial AS binaries to all

Chris Mayer
jboss1

Paid EAP branch to be available for free, as JBoss attempts to satiate disgruntled community members.

Red Hat division JBoss have made the binaries for their Enterprise Application Platform available to developers within the community.

The decision, detailed by JBoss Director Mark Little, means that once JBoss begin to commercialise each major community edition of JBoss Application Server, they will now release all relevant EAP builds to developers for free.

The latest release is now called JBoss EAP 6.0 Alpha 1, rather than AS 7.2, with the commercial product builds becoming a superset. The download processes and license for EAP will also change to make it easier for developers to test out.

JBoss say that an Alpha release in EAP is equivalent, or better, than that of a community Final release. Following that, developers can get their hands on a EAP beta release, under a “zero-dollar developer subscription”.

It’s a big shift in JBoss/Red Hat policy. Previously, there were separate builds for the enterprise and community versions of the application server. With EAP taking precedence over the other in terms of support, those using AS 7 felt short changed by the restrictive model, as they were unable to access to the product builds and provide feedback to the development team immediately.

“The net result is that everyone gets to experience the product whether or not they buy a full subscription with support,” explains Little, adding that it is “a great step in the evolution of JBoss/Red Hat.”

The JBoss FAQ page says that there are no restrictions on how developers can use the binary released under a LGPL license, but strongly advise not using it in production without a contract with JBoss.

Last year, JBoss held a vote to rename JBoss AS, with the shortlist announced at Devoxx in November. The winner, as chosen by the public, is due “early in 2013”.

The change in direction from JBoss should be applauded and it is a good first step in bringing the two communities on a par in terms of support, and hopefully bring back those in the JBoss community left out in the cold by the old structure.

Author
Comments
comments powered by Disqus