The first milestone of Vex 1.1 was published some months ago (if you don’t know Vex yet: it stands for Visual Editor for XML and is an Eclipse XML editor with a word processor like interface). Since then Carsten Hiesserich has joined the project team and mainly works on Vex’s built-in support for DocBook.
One month ago, with the second milestone we switched to Kepler. Unfortunately, the Eclipse Marketplace showed a couple of “one or more required items could not be found” errors and the number of milestone installations fell below 100 per month for the first time. So we decided to switch back to Juno (Eclipse 3.x) only for Vex 1.1, which is scheduled to be released in June 2014.
A couple of bugs have been fixed for DocBook support. In addition, in the Outline View there are now buttons to toggle the visibility of inline elements ( block elements are always shown), of processing instructions, of comments and of the first part of the contained text:
The Vex project has started to use Gerrit, a code review system which is used by other Eclipse projects, too. Vex also has a new separate Hudson instance which is required by Gerrit to veto a commit on failing JUnit tests. And this is Gerry, not to be confused with Gerrit, a young tomcat loafing around and vetoing my coding by walking over the keyboard from time to tim111111111111klllllllllllllll
Don’t be a fraidy-cat and get Vex 1.1 M3 with the new features and maybe new bugs! 😉
Drag to install: (or use Update Site http://download.eclipse.org/vex/milestones/1.1/)