Almost showtime

Vert.x 2.0 arrival imminent

Chris Mayer

The asynchronous JVM framework looks set for a regeneration, following a long period of transition to the Eclipse Foundation.

After months of arduous work, JVM application
framework Vert.x is
almost ready for its Eclipse
following the arrival of a second release
candidate for 2.0.0.

Project lead Tim Fox
detailed the

numerous bug fixes
in Vert.x 2.0.0 CR2,
work on running Netty
smoothly. Barring any
serious issues with the candidate, Fox revealed that Vert.x 2.0
Final will be available next Monday (July 8).

The project, dubbed the JVM’s alternative to
node.js, quickly became one of the most watched Github projects in
2012 for its fresh approach to application development. It hit the
headlines back in January, when VMware, who led the early
development of Vert.x, attempted to assert the project’s IP rights,
as Fox had transferred to Red Hat.

Seeing the squabbling as detrimental to the
community, Fox recommended housing the project at a neutral open
source foundation to protect Vert.x’s future. After much
discussion, the asynchronous framework found solace at the

Eclipse Foundation
, with
Fox asserting
that Eclipse’s “full service”
and “business friendly” approach would be the best fit for the

The project has already made its mark on the
Eclipse Foundation, whose decision to

move all development trunks to GitHub
influenced by Vert.x’s example.

Of the features
targeted for the next version
last November,
most appear to be present. Language support is now

into optional modules, with
each module having its own classloader. IDE integration with
Eclipse and IntellliJ is much improved (“
according to Fox in May), while the inclusion of Scala support is
good to see. The addition of a

Clojure module
will have to wait, as none of
the core Vert.x team have the desired skills to make it

Vert.x’s main website has
been given a fresh lick of paint ahead of its imminent arrival too.
Vert.x’s binaries are available on
with all the official jars on
and modules on Github.

comments powered by Disqus