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/)
Overall, the 12 Kepler packages have now been downloaded one million times. On average, one million times in less than 18 days means one every 1.5 seconds. Wow!
In Kepler the Eclipse for Mobile Developers package is missing and the Classic package has been replaced by the Standard package which contains now the Marketplace client and Git. The first three most downloaded packages are all about Java development and have together a market share of more than 80%. The first non-Java package is the Eclipse IDE for C/C++ Developers with 6.5% market share.
The 13 Juno packages were downloaded approximately 28 million times (R, SR1, SR2 summed, Classic estimated). That was even one every 1.1 seconds. But in contrast to Kepler Eclipse 4.2.x was counted as the Classic package. In Kepler Eclipse Standard is not the same as Eclipse 4.3.0 and is not included in this calculation.
The following is an incomplete list of Kepler articles of news websites (no blog posts). Please add a comment if you know of any more articles.
- InfoQ: Eclipse Kepler released (by Alex Blewitt)
- The H Open: Eclipse Kepler enters public orbit
- JAXenter: Can Eclipse Kepler get the platform back on track?
- InternetNews.com: Eclipse Kepler Orbits 71 Open Source Projects and 58 million lines of code
- DZone Javalobby: Eclipse Kepler Release: By the Numbers (by Wayne Beaton)
- InfoWorld: Annual Eclipse ‘release train’ arrives with Java EE 7, BPM backing
- heise online: 71 Projekte bei Eclipse Kepler
- golem.de: Eclipse “Kepler” ist freigegeben
- JAXenter: Eclipse Kepler Rundblick (by me)
- WAZ: Eclipse “Kepler” ist fertig
- LINUX MAGAZIN: Eclipse Kepler unterstützt Java EE 7 und Big Data
- PRO-LINUX.DE: Eclipse Kepler freigegeben
- COMPUTERWOCHE: Eclipse “Kepler” ist fertig
- JDN: Eclipse Kepler : Java EE 7 et développement en mode web au programme
- Silicon: Eclipse 4.3 Kepler : Java EE 7, BPM, Big data et IDE web
- Toolinux: Sortie officielle d’Eclipse Kepler
- Programmez.com: Eclipse 4.3 Kepler
Some hours before the release I sent e-mails to four German news websites that did not write about Juno last year, telling them when Kepler will be released, where the official press release will be published, some basic information, that they could use my bar chart and links for further reading. Two of them indeed published Kepler articles – a success rate of 50%.
Social networks grow more and more popular in news distribution. But in contrast to social networks and blogs news websites reach an extended audience. That is why I think that such news articles are important for us. Maybe next year we could send the official Luna press release upfront to the news websites with the release time and additional information about what Eclipse is and what a Simultaneous Release is. A set of screenshots and charts would improve the attractiveness of the articles and increase the chance the news will be adopted. What do you think?
1 year – 71 projects – 428 committer – 48,000 commits – 4,786 OSGi bundles – 58 million lines of code – these are the numbers of Kepler, which is the tenth Eclipse Simultaneous Release.
Compared to its precursor, Juno, the project count remained the same (taking into account the adjusted project number of Juno from 72 to 71 after the Juno release – reflecting that EMF Query 2 was not part of Juno after all). Four projects have left (Xtend, Jetty, Virgo and Runtime Packaging), four projects have joined (Stardust, Sphinx, EMF Diff/Merge and Maven Integration for Web Tools Platform). To be more precise, Xpand is still part of Kepler but it is no longer a project of its own, Xpand became part of Xtext. The highest version jump was made by Orion: from Orion 0.5 in Juno to Orion 3.0 in Kepler.
In the Kepler year the total number of bugs that were created is lower than in the years before. This could be caused by less (open) activity or/and an increasing use of Gerrit.
The satisfaction with Eclipse is still very high (around 80%) but less than in the years before.
For detail information read my article “Mein Kepler-Jahresrückblick” (German) in the upcoming (26th July) Eclipse Magazin or in condensed form online. I will also give a talk at Java Forum Stuttgart (also in German).
PS: Please feel free to use the diagrams (attribution is nice to have but not required). I opened a bug to collect and share material to promote Kepler.
Almost ten years ago, Gary Gregory requested the feature “Text Viewer and Editor needs to support word wrap” in bug 35779. Currently, the bug has 203 comments and up to now 209 people have voted for this bug. There is only one bug that has more votes than the word wrap bug. Nevertheless, the bug is still open and probably will stay open forever.
Conclusion: The text editor patch is quite promising. There are only a few minor cosmetic issues left. The performance has to be tested. Hopefully, the patch will get applied soon by the Platform team. Good job, Florian!
Update: Florian also blogged about his proposed solution, which would be his first contribution to Eclipse.
Have you ever seen Eclipse Vex, a Visual Editor for XML, in action? The following video will give you a short impression of how to create an XML document like XHTML with Vex:
Last week the first milestone of Eclipse Vex 1.1 has become available. A core API should make it easier to use Vex as a widget in RCP or SWT applications. A lot of refactorings and clean-ups have been carried out by our project lead Florian for this new API. In Vex 1.1M1 XML comments can be added everywhere (even before or after the root element) and a couple of bugs have been fixed (see also New and Noteworthy).
To install Vex 1.1M1 drag to your running Eclipse application window (this requires the Marketplace client, which is included in all Eclipse packages except Eclipse Classic).
Today, Eclipse Vex 1.0 (drag to install), the Visual Editor for XML, has been released. The release and graduation review has been successfully passed. No egg anymore, which indicates incubation project phase.
John Krasnay started the Vex project at SourceForge in 2002. In December 2002 Vex 0.1 was released as a Java Swing application (see screenshot below) that provides a word processor-like interface for editing XML documents. The first Eclipse-based version was Vex 1.0, which was released in July 2004. In April 2005 version 1.2.1 was released. Then the project became inactive.
In 2008 David Carver migrated the project to Eclipse or – to be more precise – into the Eclipse Web Tools Platform (WTP) Incubator Project. In 2009 I became committer and Florian Thienel joined in 2010. In 2011 Vex became a project on its own in Mylyn Docs led by Florian, the most active developer.
In the last 10 years many people have contributed to Vex. Thanks to all those people Vex is reborn in version 1.0 again. Happy birthday Vex!
Tobias Althoff, Susanne Könning and Ji Shin, computer science students at the University of Münster, have developed the Eclipse Search CSV Export plug-in. It is their very first Eclipse plug-in, which was originally created for Pacx, the Platform for Annotated Corpora in XML. But it can be used in Eclipse and other Eclipse based application as well. Since I was only their guide to the Eclipse universe, I would now like to yield the floor to the real authors:
Do you know this feeling? You are searching something, find it, and then… then what? You don’t have any way to use your Eclipse search results in another program. Wouldn’t it be wonderful to be able to export your results into a *.csv file?
Guess what! That’s possible now. We proudly present the CSV Export Plug-in for the Eclipse File Search.
Tobias Althoff, Susanne Könning and Ji Shin
72 projects contributed 55 Million lines of code to the ninth Simultaneous Release, more projects and more code than in the years before. Even if the bars are adjusted to reflect the more fine-grained project structure since Indigo in 2011 this is quite impressive:
But will Eclipse and the Simultaneous Release continue to grow? Since the beginning of Eclipse 10 years ago the number of active committers and active projects has increased from year to year. In the Juno year 14 new projects have been created in contrast to 13 projects that have been terminated. The total number of projects stays at around 200. But the equivalent number of projects has created more bugs than in the year before:
PS: Please feel free to use the diagrams (attribution is nice to have but not required). Let me know if you would like to have the diagram as SVG or translated.