Announcing Orion 8.0

by John Arthorne at February 27, 2015 08:04 PM

The Orion Project is pleased to announce the release of Orion 8.0. You can check out the new release now on OrionHub, or grab your own copy of the Orion server from the download page. The Orion Node.js implementation matching this release is orion 0.0.35 on NPM. The Orion 8.0 release includes over 1000 commits from 36 unique contributors, and fixing 280 bugs. The major themes for this release were building higher value tools for JavaScript/CSS/HTML development, and in making the Orion server highly scalable.

In language tools, Orion 8.0 introduces Quick Fixes for automatically resolving common coding problems, semantic file to file navigation, smart language tool hovers, and many more smaller enhancements. For complete details on the extensive web tooling improvements, read Orion 8.0 Language Tooling Enhancements Part 1 and Part 2

On the server side, the main focus for Orion 8.0 has been on clustering support. For a site with heavy traffic, it is useful to have multiple Orion instances operating on the same Orion workspace content. This also allows you to have a running standby instance for fail-over and upgrade without any site downtime. To support this, Orion 8.0 has introduced file-based locking to manage contention across multiple instances. In addition, persistent state has been divided between instance-private and shared locations, to prevent sharing of the server’s own internal state that is not designed for sharing across instances.

A final major change on the server side was completely rewriting our search infrastructure. The new Orion search implementation provides global search and replace based on a server side search crawler, rather than indexing. This means searches take a little longer, but they have perfect accuracy. Server side search now also supports regular expressions and case-sensitive search, making this kind of search much faster than before. This implementation also simplifies Orion server management for large-scale Orion installs, because it saves Orion server admins from having to deal with search index sharding and Solr clustering. This server side global search is currently only available on the Java implementation of the Orion server, but there is a team in the community working on a Node.js implementation for this as well.


by John Arthorne at February 27, 2015 08:04 PM

Eclipse Luna SR2 - Download Now

February 27, 2015 03:21 PM

Eclipse Luna SR2 (4.4.2) is now available!

February 27, 2015 03:21 PM

WTP 3.6.3 Released!

February 27, 2015 03:05 PM

The Web Tools Platform's 3.6.3 Release is now available! Installation and update can be performed using the Luna Update Site at Releases 3.6.3, 3.6.2 and 3.6.1 fix issues that occur in prior releases or have been reported since 3.6's release. WTP 3.6.3 is featured in the Luna SR2 Eclipse IDE for Java EE Developers, with selected portions also included in other packages. Adopters can download the build itself directly.

More news

February 27, 2015 03:05 PM

Improved JBoss Fuse Tooling coming soon…

by lhein at February 27, 2015 12:56 PM

I am happy to announce some of the highlights of the upcoming release of the Red Hat JBoss Fuse Tooling. It will be available via early access in the JBoss Tools Integration Stack 4.2 / Developer Studio Integration Stack 8.0.

What is new?

There are a lot of improvements and bugfixes and I just want to pick the most important things for now. You can see a full list of changes in the What’s New section for the release.

Apache Camel Debugger

You probably already used the tracing functionality for a running Camel Context, but now we are happy to finally give you a Camel Debugger. Using the Eclipse Debug Framework we created our own Camel Debugger which works fully through the design view of the Camel editor. Here you can set your breakpoints (static and conditional ones) and breakpoints hit are highlighted in your design view. Instead of using the "Run as → Local Camel Context" menu you can now use the "Debug as → Local Camel Context" to startup the Context in debug mode. Once a breakpoint is hit Eclipse will automatically change to the Eclipse Debug perspective.


Step through your routes, add watch expressions, change message content on the fly or simply monitor what your routes do with the messages. Add a conditional breakpoint if you only want to debug on a certain condition. You choose the condition language and you setup the condition in an easy to use expression builder.

Palette and Properties

Over the past weeks we worked on improvements regarding the usability of our Camel Route Designer. The result of that work is that we introduced a new drawer to the palette of the designer which provides easy to use items for Apache Camel Components. In the past you had to know that the Endpoint palette entry has to be used to create a connector for a Camel component just by prepending the right protocol name to the endpoints uri attribute field. That still left you alone in adding the correct Maven dependency to your projects pom.xml. When you now drop a component connector to the route the pom.xml gets updated automatically so you don’t need to care any longer.

New Palette

Starting with version 2.14 the Apache Camel developers started implementing a model to determine URI parameters and their meta data. We now use the provided functionality to give our users improved property pages for the Apache Camel Components.

Advanced Properties

(the above image shows the properties for a file connector endpoint)

Server Adapters

Our server adapters have been reworked and we now provide adapters for the latest version of Apache ServiceMix, Apache Karaf and JBoss Fuse.

New Server Adapters

The wizard pages for creating the servers have been reworked too and you are now able to download the binaries directly from within your Eclipse session.

New Wizard Layout

Another thing to mention is that we replaced the old deployment options in favor to the modules publishing way using the servers view. You can select the server entry there and choose to Add or Remove modules to/from the server. The deployed projects from your local workspace will be visible as a child node under the server item. Depending on your settings for the server publishing options your application will be republished automatically when it gets out of sync / is changed locally.

I hope you enjoy the new stuff. Have fun!

Lars Heinemann

by lhein at February 27, 2015 12:56 PM

Gimp 2.8 – Eclipse Splash

by eselmeister at February 27, 2015 08:19 AM

I was wondering why the splash screen is not visible anymore after using Gimp 2.8 to create the *.bmp file. It’s the color profile option that needs to be deactivated. Here’s the workflow:

Create a splash design with Inkscape:

Width: 455 px
Height: 295 px

Export the design to *.png format (90 dpi).

Splash Inkscape

Then open the *.png file with Gimp and export it to *.bmp format.

Splash Gimp

Use the options:

> Don’t write color information
24 Bit
> R8 G8 B8

That’s it :-).

by eselmeister at February 27, 2015 08:19 AM

New Eclipse Chain Completion Improvements and Hippie Privacy Settings

by Simon Laffoy at February 26, 2015 09:15 AM

Codetrails has just released Eclipse Recommenders 2.1.12 and Codetrails Connect 1.3.0. So what’s new? Let’s have a look ...

by Simon Laffoy at February 26, 2015 09:15 AM

Eclipse N!

by waynebeaton at February 26, 2015 04:29 AM

The Eclipse Planning Council—with help from the community—is trying to sort out the name for our eleventh named simultaneous release in 2016. We had some trouble with the first set of names that we selected, and so we’re into the second round.

The Lynn Lobby has significant momentum.

The “Eclipse Lynn” Lobby has significant momentum.

We started following the alphabet a few years ago, naming our fifth release “Helios“, and now we’re up to the letter N. We’ve been bouncing around some N names on Twitter; I quite like the idea of just going with “N”, and stated as much.

I originally put in the exclamation mark to make it seem more exciting, but then it occurred to me that the exclamation mark has special meaning in Lisp. In a functional programming language like Lisp, you generally avoid changing state, so Lisp functions that make changes are marked with a cautionary exclamation point (spoken as “bang”). When you invoke a bang function, things are going to change:

It seems appropriate. Change is in the air. I’m excited by the prospect of having an actual installer. I’m excited by our vision of the future of the developer’s platform.

With Mars, our June 2015 release, we’re making a subtle shift to put more focus on the user experience. This takes the form of our Every Detail Matters for Mars effort which aims to tackle a handful of “little things” like getting more of the default preferences right in our packages, standardizing naming conventions, providing reasonable and useful package-specific new and noteworthy documentation, improving the story for adding simultaneous release plug-ins into an Eclipse-based IDE, and more. I’m pretty excited about some bits of the “and more” part, but I’ll save that discussion for another day.

Of course, we’re also trying to tackle some pretty big things. We’ve come a long way towards having a proper installer for Eclipse. I’m also optimistic that we’ll be including Gradle support in Eclipse (more on this later).

We need your help and so we’ve started the Great Fixes for Mars skills competition. To enter, all you need to do is take responsibility for a bug, mark it as “greatfix”, and submit a patch. We’ve even provided a list of great suggestions where you can make the biggest impact. There’s prizes. Cool prizes.

Enter the Great Fixes for Mars skills competition; there'll be prizes!

Enter the Great Fixes for Mars skills competition; there’ll be prizes!

This shift in momentum will build through Mars and into the 2016 release. I’m certain that N-bang will usher in even bigger changes.

But what do I know? I’m just an Old Dude Who Knows Smalltalk (and Lisp).

EclipseCon 2015

by waynebeaton at February 26, 2015 04:29 AM

You can Fork & Clone a Repo from Fork Visualisation View

by Its_Me_Malai ( at February 26, 2015 12:24 AM

Having added the functionality of visualising Repositories that are online thru Fork Visualisation View, the next usecase was allowing them to the forked into our login and also clone into our eclipse git perspective.

We have now fixed this requirement. You may Fork a Repository from the Fork Visualisation View to your login and also clone it to add to your Git Repositories.

Screenshots as shown below

A new button is available on the Action Bar of the View. Select the repo that you want to Fork and click on this Fork and Clone action.

On successful Forking, this message would he sbown asking for Clone Confirmation. If clicked on YES, it opens the Clone dialog with the required URL filled as it is done on Paste in Git Repositories view.

It is available for download from MarketPlace :
Code is available on

Enjoyin Eclipsing until we meet next time.


by Its_Me_Malai ( at February 26, 2015 12:24 AM

Announcing J2V8 2.0

by Ian Bull at February 25, 2015 06:18 PM

Last year I announced J2V8, a new JavaScript engine for Java that wraps V8 with a set of Java Bindings. We have been using this technology to power Tabris.js on Android — giving us much better performance than Rhino could. While J2V8 was very stable, it wasn’t very easy to consume. Today I’m happy to announce that J2V8 2.0 has shipped, and it’s much easier to embed in your Java Applications.

There are several notable improvements in J2V8 2.0:

Self Loading Native Libraries

Following the lead of SWT from years ago, we have included a Library Loader that will load the native library automatically for you. You no longer need to twiddle with the java.library.path to get J2V8 to work. This also works on Android.

Bundled Native Libraries

The native libraries have also been bundled with the Jar file. Currently we are shipping 5 different Jar files for J2V8:

The final one (j2v8_android.jar) contains the native library for both armv7l and x86, so you can use it on several different Android devices. By adding the jar to your classpath and calling V8 runtime = V8.createV8Runtime(); (V8.createV8Runtime(null, activity.getApplicationInfo().dataDir); on Android: because you need to specify the location to unpack the native library) the native library will be automatically loaded for you. We can add more platforms, but each one takes time as I need to build V8 on the platform first. Any particular platform I should target next?

Available in Maven Central

J2V8 is now available in Maven Central. You no longer need to build the library yourself. For example, add the following snippet to your pom.xml to use J2V8 on MacOS:


Hello, World

Once you’ve added the the dependency to your pom.xml, you can begin embedding JavaScript in your Java Application using J2V8. Here is a simple Hello, World! that demonstrates how to call JavaScript from Java and register a callback.

package com.example;
import com.eclipsesource.v8.V8;
public class Hello {
	public void print(String s) {
	public void start() {
		V8 v8 = V8.createV8Runtime();
		v8.registerJavaMethod(this, "print", "print", 
                                      new Class<?>[] { String.class });
		v8.executeVoidScript("print('Hello, World!');");
	public static void main(String[] args) {
		new Hello().start();

Screen Shot 2015 02 25 at 9.56.47 AM Announcing J2V8 2.0

More Information

I will presenting J2V8 at EclipseCon in San Fransisco on Thursday March 12th. Stop by and say hi if you’re in the area.

Finally, if you want to try it on Android without embedding it into your own Java application, request an invite to Tabris.js.


Leave a Comment. Tagged with tabris.js, tabris.js

by Ian Bull at February 25, 2015 06:18 PM

Release Engineering special issue now available

by Kim Moir ( at February 25, 2015 03:26 PM

The release engineering special issue of IEEE software was published yesterday.  This issue focuses on the current state of release engineering, from both an industry and research perspective. Lots of exciting work happening in this field!

I'm interviewed in the roundtable article on the future of release engineering, along with Chuck Rossi of Facebook and Boris Debic of Google.  Interesting discussions on the current state of release engineering at organizations that scale large number of builds and tests, and release frequently.  As well,  the challenges with mobile releases versus web deployments are discussed. And finally, a discussion of how to find good release engineers, and what the future may hold.

Thanks to the other guest editors on this issue -  Stephany Bellomo, Tamara Marshall-Klein, Bram Adams, Foutse Khomh and Christian Bird - for all their hard work that make this happen!

As an aside, when I opened the issue, the image on the front cover made me laugh.  It's reminiscent of the cover on a mid-century science fiction anthology.  I showed Mr. Releng and he said "Robot birds? That is EXACTLY how I pictured working in releng."  Maybe it's meant to represent that we let software fly free.  In any case, I must go back to tending the flock of robotic avian overlords.

by Kim Moir ( at February 25, 2015 03:26 PM

Eclipse Scout Roadmap 2016

by Matthias Zimmermann at February 24, 2015 09:19 PM

For the 2016 release of the Scout framework we will introduce two significant changes. These changes address major pain points we have suffered from in the past. As the scope of the two changes is substantially larger than in previous releases, we would like to start talking about them well ahead of time. So remember in the text below that this is a blog about the future of Eclipse Scout scheduled for 2016, not about the upcoming Mars release.

The first change is driven by our vision of the future of UI technologies for business applications. The second change addresses the need of our customers and BSI that Scout applications should be easy to integrate in a Java EE or Spring based environment. In the text below we will discuss these two changes individually.

A new HTML5 Renderer

The first change is based on our belief that the future of business applications mostly lies in the domain of web applications. In consequence, Eclipse Scout needs to provide the best possible web experience for the users of Scout applications. And to achieve this goal for the 2016 release, we already have started to write a new Scout web rendering engine, directly based on HTML5/CSS3 standards. Thanks to this substantial investment of BSI, Scout applications will comply with the new de-facto standard for web applications and will be able to take advantage of the latest web technologies in the future.

This decision also implies that future Scout web applications are no longer based on the Eclipse RAP project. At the same time, discussing this topic extensively with our customers, we found that their demand for the existing Swing and SWT rendering components no longer matches the necessary expenses to maintain these components. This is why we decided to discontinue the Scout SWT and Swing desktop rendering components after the Eclipse Mars release.

Eclipse Scout will become a Java framework

The second change affects the foundation of Eclipse Scout applications. Currently, Eclipse Scout applications are based on OSGi and the Eclipse runtime platform. In the past, we have addressed the challenge to integrate a plugin based application with Java EE technologies again and again. And according to some Scout customers, integrating the plugin based Scout server with Spring technology did cost them significantly more time than anticipated.

Observing the market and the need of our customers over the past years, we have come to the conclusion that Scout’s dependencies to OSGi/Eclipse platform did bring more harm than good to Scout projects. This is why we now started to implement replacements for familiar Eclipse concepts such as jobs, extension points and services.

As a result of this second change, Eclipse Scout applications will become standard Java applications that will seamlessly integrate with Java EE technologies and other Java frameworks, such as Spring. We also hope that this change will increase the adoption of Eclipse Scout in the Java domain.

What will stay the same?

Although the changes mentioned above may seem substantial, it is important to keep in mind that most aspects of the Eclipse Scout framework remain the same.

  • Scout will continue to be an Eclipse Open Source project.
  • The Scout SDK will continue to be based on the Eclipse IDE.
  • The existing Scout application model will (mostly) stay as it is.
  • Migration efforts for existing Scout applications will remain rather modest (with the exception of the rendering part for your custom controls, if any).
  • From the Scout developer perspective these changes will probably not feel exciting. But this is by design.
  • And to avoid confusion: The Scout Mars release will still be shipped with the known RAP, SWT, and Swing rendering components.

Your Feedback?

Whether you like these changes or are concerned regarding your plans for Eclipse Scout please let us know. Please contact us on the Scout forum. For discussions we have created separate topics. One for the new HTML renderer and another one for removing the Eclipse/OSGi dependencies.

If you prefer a less public channel for discussing these changes you can contact us by email to Your feedback is very valuable to us and we would like to find/discuss options if you have any concerns or questions.

More Blog Posts to come

  • History of Scout and its supported technologies
  • Current state of the new HTML5 rendering component
  • Progress reports on becoming a Java framework

Scout Links

Project Home, Forum, Wiki, Twitter

by Matthias Zimmermann at February 24, 2015 09:19 PM

Let's put Orion into Context !

by Eric Moffatt ( at February 24, 2015 09:05 PM

OK, try 2 (for those that noticed my earlier, empty, post...;-).

A small aside to start:

I've recently joined the Eclipse Orion team; after >10 years on the eclipse platform it was time for a change. Working on the eclipse UI was easily the highlight of my career so far. The opportunity to work with many truly exceptional people in such an energetic ecosystem made the work even more rewarding. While I missed out on EclipseCon this year I *will* find my way to at least one more so that I can properly thank (in person...with Beer !) at least some of the crew that has been instrumental in moving eclipse forward over the years; far too many to name know who you are..and thanks !!

Now on to the future and Orion...

It took me literally no time at all to realize that Orion needed some tooling work. Immediately upon my first attempt to work on some JS code I realized that the tooling that made me look effective in JDT just didn't exist. I was reduced to regex searches and the like to wend my way through the maze of JS / CSS / HTML files comprising Orion. This made going up the learning curve for the codebase seem more like climbing a mountain of molasses. Something had to be done...

...and has ! Take a look at the Orion 8 N&N to see the new tooling in Orion 8 and for those lucky enough to be at EclipseCon don't miss Simon Kaegi's talk: "JavaScript Language Tools. In Orion.". These are just the first fruit of the efforts to make the Orion editor more that just a fancy notepad, more are on the way.

Since the new functionality has already been announced  this post will look more closely at where we're going with the tooling. It's worth noting that all the Orion 8 feedback needed was a change in how the existing hover tooltip got its information and 'quick fix' commands (pretty good bang for the buck IMO).

It's all about the context

Most of the help from JDT comes from its crawling large statically analyzed parse trees(AST's). Since this is largely impossible in JavaScript what can we do ?

There are (loosely speaking) three different types of tooling feedback:

Information: Regular tooltip style giving JSDocs or showing a color when hovering over parts of a

Manipulation: The is for feedback that allows the user to modify their files in some way (think quick fixes and, eventually, refactoring and color/font definition).

Navigation: This is the ability for the editor to recognize and locate files referenced from the one they're editing.

Of these three the one that is most important is 'Navigation'. One of the first problems we encountered was that the code is (of course) always written reflecting the directory structure of where it is *deployed* (i.e. where it lives on the server). In cases where anything but the 'null' deploy is used (the code is in the same structure for development as it is when deployed) we needed some sort of 'File Map' to allow us to properly locate the development file given a reference in a deployed file. This is currently available through the file navigation hovers in Orion 8 but this is just the beginning. It's more than just 'require' and 'import' but should also be capable of deeper introspection such as locating a specific CSS class used in a JS snippet that is assigning a class to a classlist (by searching the available CSS classes for that specific class name).

With the ability to navigate from 'required' references in one file to the actual JS (or 'imported' CSS files) we also gain the ability to walk dependencies looking for useful info to show the user (i.e. JSDoc content assist for methods declared in a required JS file...). As we become more proficient in parsing relevant info we will start to gain the ability to answer some of the trickier questions like "Where is this JS / CSS class used ?" and "Where is this method used ?" (needed for eventual refactoring).

Orion 9 and beyond

Here are some of the things we'll be focused on for future releases...

Type Inferencing

Due to its inherently mushy nature JavaScript is effectively tooling resistent. Our goal is to not
restrict what the developer wants to do but instead warn them if they're doing something that will
make the tooling ineffective. For example Orion uses RequireJS to access instances of various JS
services. The 'required' service instances are assigned to variables in the object doing the requiring. The tooling will work only if the code never assigns a different, unknown, value to this var. To help here the tooling will produce a warning should such an assignment be used (preventing us from doing content assist...on that var).

Note that can (and should) be generalized to account for new techniques to 'typify' JS. If we parse a 'type' (whether from JSDoc or some other type description) the underlying mechanisms will be common enough to show the warning any time a 'typed' var is assigned to regardless of how that type was originally specified (unless of course the value being assigned is of a matching type).

Deeper Context Introspection

It's the union of all the references within a web project that truly define its 'context'. Being able to infer as much as possible about the resources being used in a particular scenario is proportional to the tooling support we can provide. One of the possibilities we're looking at is the ability to specify the HTML doc we're doing our development in the context of. This would provide access to the specific CSS files used by that page (which may be different from those used on a different page), allowing us to provide more accurate feedback; in the end everything has some page at its root.

Since the tooling relies heavily on the file map we'll be making it simpler to create and maintain the map for your particular setup as well as providing this functionality 'in the UI' (i.e. allowing the user to define explicitly the file being referenced and having the UI remember this choice, some sort of support people writing the deploy scripts...). The goal here is to make this as simple (for you) as possible so that the advantages of having access to great tooling far outweigh the effort needed to provide the file map for your project.

As a complete noob to the Web development world one of the first differences I noticed is that web pages are the result of the *merge* between the HTML, JS and CSS files. I found that working on these files in separate tabs was a pain. We'll be working on various ways of allowing the coder to focus more closely on working and less on navigation issues. I don't think it'll take 10 years to show multiple editors on one tab within Orion...;-).

What I'd like to see is something like this:

This uses everything we've seen so far. Type inferencing tells us that '_thumb' is a DIV, meaning that we can infer that 'splitLayout' is a CSS class name. We can then search in the appropriate CSS files to locate the actual CSS class and extract it to show in the tooltip. Ideally in this scenario the tooltip would allow you to edit the contents of the class to allow you to 'tweak' it without ever having to open it.

I wish that this was available when I started...;-)

by Eric Moffatt ( at February 24, 2015 09:05 PM

Announcing Sapphire 8.1.2 Release

by Konstantin Komissarchik ( at February 24, 2015 08:21 PM

On behalf of all who contributed, I am very proud to announce the availability of the Sapphire 8.1.2 release. This release includes a number of fixes, mostly in the area of accessibility.

by Konstantin Komissarchik ( at February 24, 2015 08:21 PM

New service release for EMF-IncQuery 0.9.1

by ujhelyiz at February 24, 2015 04:19 PM

We have made public a new service release EMF-IncQuery 0.9.1, that fixes a few issues that were found after the last release. It is recommended for every user of EMF-IncQuery 0.9.0 to update.

by ujhelyiz at February 24, 2015 04:19 PM

Eclipse Newsletter - Develop for the Cloud, in the Cloud

February 24, 2015 02:19 PM

Read up on Orion 8 and Che, projects building web-based tools for software developers, and Codefresh's innovative use of Orion.

February 24, 2015 02:19 PM

JBoss Tools Alpha1 for Eclipse Mars

by maxandersen at February 23, 2015 09:12 PM

Happy to announce first Alpha build for Eclipse Mars M5.

Downloads available at JBoss Tools 4.3.0.Alpha1.


This version of JBoss Tools targets Eclipse Mars 4.5 (M5).

We recommend using the Eclipse 4.5 JEE Bundle since then you get most of the dependencies preinstalled.

Once you have installed Eclipse, you use our update site directly:

Note: Marketplace entry and Integration Stack tooling will become available from JBoss Central at a later date.

What is new ?

As always there is more than can be covered in a single blog but here are some of my favorites. You can see everything in the What’s New section for this release.

Java EE 7 Batch and CDI Support

The initial work on providing a structured editor for Java EE 7 Batch job.xml files are in. The editor is based on Eclipse Sapphire and over time we want to extend it for smarter content assist both in the structured editor but also in the source view.

Java EE 7 Batch Editor

Furthermore for Java EE 7 we’ve now added auto enablement of CDI for Java EE 7 projects. Meaning the tools also now honor Java EE 7 CDI spec about no longer requiring beans.xml for activating CDI.

BrowserSim Standalone and iPhone 6 skins

BrowserSim adds skins and layout for iPhone 6 devices.


These skins and others are also available in BrowserSim Standalone mode which allow you to run Browersim without depending on a full Eclipse install.

You can use this "oneliner" to try it out:

curl -L -o && unzip && java -jar browsersim.jar

If you are on OSX you need this one:

curl -L -o && unzip && java -XstartOnFirstThread -jar browsersim.jar

We’ve extended the HTML5 palette to allow easier adding of often used html5 elements.


This grew the palete to be rather big thus we came up with adding a 'Most popular' slot so you always have easy access to the elements you used most often.

The following video shows how that works.

FeedHenry support

If you are a FeedHenry user we’ve now added support for easy importing and running of your FeedHenry Cordova applications.


Windows Phone support

Apache Cordova support now includes support for Windows Phone projects (requires you to run on Windows still though :)


This also adds support for running Windows Phone Emulator.

Hierarchical projects

This feature is actually part of Eclipse M5 and not directly JBoss Tools but I wanted to mention it because the feature is awesome and it was contributed by us by the great work of Mickael Istria.

In Eclipse M5 the Project Explorer now have a "Projects Presentation" in its view menu. Allowing you to switch from the traditional "Flat" view to the new "Hiearchical". This new option lets you view the projects as they are structured on the filesystem as opposed to one big flat list.

Flat vs Hierarchical projects

This is especially super helpful for those who have large multimodule Maven projects. Now you can get some sanity back.

Next steps

While we wait for feedback on Alpha1, we are already working on what will become Alpha2. Some of the things that are moving here are:

  1. OpenShift v3

  2. Docker Tooling

  3. Better JavaScript content assist

  4. Deprecate/remove visual JSF page editor, focusing on html5 preview

  5. Making project imports in Eclipse simpler

  6. And more…​

As always, ask/suggest away and we’ll keep you posted!

Have fun!

Max Rydahl Andersen

by maxandersen at February 23, 2015 09:12 PM

Open Source Reporting Comparison BIRT, Jasper, Pentaho - Third Edition

by Scott Rosenbaum ( at February 23, 2015 08:07 PM

Innovent Solutions has performed periodic comparisons of the reporting portion of Eclipse BIRT, Jaspersoft and Pentaho starting in 2010 with an update in 2012. In 2015, we have decided to revisit the reporting products to evaluate what has changed and to update our comparison.

To see the full review please visit our website to read the articles:

by Scott Rosenbaum ( at February 23, 2015 08:07 PM

EMF Forms Developer Tooling: Debugging

by Maximilian Koegel at February 23, 2015 06:47 PM

EMF Forms makes it really simple to create forms to edit your data. To get started please refer to our tutorial. We have recently released EMF Forms 1.5.0, which will also ship with the Eclipse Luna SR2 Modeling Tools. For this release we put a focus on improved developer tooling. This involves the View Model Editor and Error Reporting in the run-time. This blog post will describe one particular feature in the run-time: improved debug output.

In default mode EMF Forms is resilient to failure and will try to render as much as possible even in the presence of ill-configured view models and the like. This is good for production but not so nice if you would like to diagnose a problem while still developing your application. Therefore we provide a debug mode for the run-time. If you set “-debugEMFForms” as a program argument you can instruct the EMF Forms run-time to run in debug mode. This will provide detailed output in case of problems.

23 02 2015 19 31 43 EMF Forms Developer Tooling: Debugging

For example if a renderer fails to render something, a view model fails to load or a domain model references is invalid and fails to resolve, EMF Forms will report those failures rather than falling back to default behavior. This should help with finding the culprit…;)

23 02 2015 19 50 14 EMF Forms Developer Tooling: Debugging


Leave a Comment

by Maximilian Koegel at February 23, 2015 06:47 PM

PolarSys stellt 5 neue Open Source Lösungen für Systems Engineering vor

February 23, 2015 03:11 PM

Die Eclipse Foundation und PolarSys, ein Industrie Konsortium (“Working Group”) innerhalb der Eclipse Foundation, liefert nun 5 neue Lösungen für die Entwicklung von eingebetteten Systemen.

February 23, 2015 03:11 PM