JavaScript Linters, even in your IDE!

by vasanthis at May 23, 2016 05:34 PM

What is a Linter?Linters are Code Quality Inspectors, which work by basically parsing your code. They check JavaScript code for common mistakes and discrepancies without running the application.You can plug linters into your code editor or copy and paste your code into any standard online linting tool. Linting your code is a great thing to […]

The post JavaScript Linters, even in your IDE! appeared first on Genuitec.

by vasanthis at May 23, 2016 05:34 PM

Eclipse Demo Camp Neon, June 20th 2016 – Already sold out?

by Maximilian Koegel and Jonas Helming at May 23, 2016 10:42 AM

Every year it is amazing to see how fast the Eclipse DemoCamp in Munich sells out. To give everyone a fair chance to register, we have announced the time the registration opens in advance. This year, it took less than 24 hours, until the available 110 seats were fully booked. However, even if you did not get a seat, we still encourage you to register for the waiting list. You can register here. There you’ll also find detailed information on the location, agenda, time and more. The democamp is in 4 weeks (June 20th 2016) and some of the 110 registrants will be forced to cancel. We remind all current registrants to double check their availability. We expect some people to unregister before the event. If and only if you are on the waiting list, you will be notified immediately, once a seat becomes available. We wish you good luck and we are looking forward to great demos and seeing you in June!

A big thanks to our sponsors: BSI Business Systems Integration AG,  EclipseSource München GmbH, Eclipse Foundation, Capgemini Deutschland GmbH and Angelika for organization.


Leave a Comment. Tagged with democamp, eclipse, democamp, eclipse

by Maximilian Koegel and Jonas Helming at May 23, 2016 10:42 AM

LiClipse 3.0.3 (providing back to Open Source: multiple languages/TextMate bundles in Eclipse).

by Fabio Zadrozny ( at May 20, 2016 12:19 PM

LiClipse 3.0.3 is now released... The main things on LiClipse itself is that the base platform was upgraded to Eclipse 4.6 RC1 and EGit was upgraded (it had a critical issue in the Git Staging View).

Now, what I really wanted to talk about is that with this release, the LiClipse editor component was open sourced!

The editor component in this case is the component which allows LiClipse to support multiple languages out of the box (either through its own language or through the TextMate grammar).

So, the features which are now available as Open Source (EPL) are:

  • Syntax Highlighting (LiClipse, TextMate or SublimeText based).
  • Code completion.
  • Outline view and Quick Outline.
  • Text-based mark occurrences.
  • LiClipse Languages view:
    • Enables exploring installed languages.
  • LiClipse Partitions view:
    • Enables inspecting the partitioning of the editor.
    • Useful to debug how LiClipseText is parsing a language.
  • Use LiClipseText as a base for other editors:
  • Languages may be created and experimented with on-the-fly, without restarting Eclipse.
The home page with more details on the project is:

So, what does this mean for LiClipse itself and its current users?

First, LiClipse (the commercial counterpart) still exists and provides advanced features not in LiClipseText:
  • Bundling of LiClipseText (along with PyDev, EGit, ColorTheme, AnyEdit and StartExplorer) as a standalone with native installers.
  • Enhancements to the theming (allowing theming of the IDE along with the editor and a nice dark theme).
  • Multiple cursors.
  • Linting for JavaScript, XML and HTML editors.
  • Code formatting for HTML, XML.
  • Vertical Indent Guides.
  • Improved text search capabilities (with Lucene index-based searching, support for external folders, open editors and additional filtering on results page).
  • HTML preview for the RST, Markdown and HTML editors.
  • Debugging of Django Templates in PyDev.
  • Launching of files opened with LiClipseText.
My hope is that users that can will still upgrade to it (to get the advanced features and to help in keeping the LiClipseText and PyDev development going on) or will donate to keep its development going forward...

And the main benefit here (both for existing users or new users) is that the LiClipse editor (LiClipseText) being EPL makes it hackable by anyone ;)

by Fabio Zadrozny ( at May 20, 2016 12:19 PM

Download Eclipse Neon (4.6) RC1

May 20, 2016 06:15 AM

The latest Eclipse Neon release is now available. Download and test drive it this weekend!

May 20, 2016 06:15 AM

Presentation: Moving a Large Swing-Based Geoscience Application to Eclipse

by Mike Reyes, Mary Cole at May 20, 2016 03:09 AM

Mike Reyes and Mary Cole discuss the reasons for selecting Eclipse and RCP, how the move was made, challenges encountered during this move, and the benefits that have resulted from this change.

By Mike Reyes, Mary Cole

by Mike Reyes, Mary Cole at May 20, 2016 03:09 AM

Eclipse Newsletter - JavaScript Development Tools Rebooted

May 19, 2016 02:08 PM

JSDT project has been officially rebooted! Read all about the new features and enhancements.

May 19, 2016 02:08 PM

Editor 3.x/4.x – org.eclipse.ui.editorss

by eselmeister at May 19, 2016 10:27 AM

I would like to show you how to re-use the Eclipse editor area in an e4 application. Before, I had the problem that the editor disappeared after maximizing views or that Eclipse showed me messages like:

!MESSAGE Exception while dispatching event org.osgi.service.event.Event [topic=org/eclipse/e4/ui/model/application/ApplicationElement/tags/REMOVE] {ChangedElement=org.eclipse.e4.ui.model.application.ui.basic.impl.PartStackImpl@4981d95b (elementId:, tags: [active], contributorURI: platform:/plugin/ (widget: CTabFolder {}, renderer: org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer@7b2f8152, toBeRendered: true, onTop: false, visible: true, containerData: 10000, accessibilityPhrase: null), Widget=CTabFolder {}, AttName=tags, EventType=REMOVE, Position=1, OldValue=Maximized} to handler org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler@5f32ab17
org.eclipse.e4.core.di.InjectionException: java.lang.ClassCastException: org.eclipse.e4.ui.model.application.ui.advanced.impl.AreaImpl cannot be cast to org.eclipse.e4.ui.model.application.ui.advanced.MPlaceholder
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(
at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler$

So, here’s the description how to use the editor correctly:

A) Define an Area under “Shared Elements” in the Application.e4xmi:

Application.e4xmi Area

B) Insert a “Part Stack” called “org.eclipse.e4.primaryDataStack”:

Application.e4xmi Part Stack

Add the tags:

  • newtablook
  • org.eclipse.e4.primaryDataStack
  • EditorStack
  • NoAutoCollapse

Application.e4xmi Part Stack Tags

C) Import the Area in the fragment.e4xmi:

fragment.e4xmi Import

D) Reference the Area via a Placeholder called “org.eclipse.ui.editorss”:

fragment.e4xmi Placeholder

It’s important that the Placeholder gets the ID “org.eclipse.ui.editorss”. The Area must be referenced in other perspectives via the same placeholder ID “org.eclipse.ui.editorss”.

E) The 3.x editor is used when elements are opened via the “Project Explorer”:

3.x Editor

F) The 4.x editor is used when elements are opened via 4.x editor parts:

4.x Editor

That’s it!

by eselmeister at May 19, 2016 10:27 AM

Announcing Sapphire 9.0.5 and 8.2.5 Releases

by Konstantin Komissarchik ( at May 18, 2016 10:58 PM

Sapphire 9.0.5 and 8.2.5 releases are now available. Both include a fix for the validation messages appearing out of order in some cases and a fix for the diagram editor context menu not displaying if the editor has been scrolled. Sapphire 8.2.5 is intended for adopters who are not yet able to require Java 8. Sapphire 9.0.5 will be part of the upcoming Neon release of Eclipse.

by Konstantin Komissarchik ( at May 18, 2016 10:58 PM

Eclipse Platform on Java 9 b118

by waynebeaton at May 18, 2016 06:34 PM

I’d taken a little break from testing Eclipse Platform on Java 9 Jigsaw builds. A few nights ago, I pulled down the latest builds of both and gave them a spin.

I pulled down build 118 of the 64 bit Linux version of the Java 9 JDK. The last time I did this, the Jigsaw builds were separate, but they’ve since replaced the Java 9 builds, so when you download Java 9 you now get Jigsaw. It’s currently delivered as a .tar.gz file, so I extracted it into a directory on my system.

I then turned my attention to the Eclipse Installer which has a handy feature that hunts down JREs installed on your system and lets you pick the one that you want to use. It also has a handy feature that lets you manually add JREs to the list. The installer includes some logic to help the user avoid making a poor choice, and changes in the way that the JRE reports its version means that the installer doesn’t recognise this particular version of the JRE as a JRE and won’t let you select it (see Bug 493759). I decided to install the latest Neon M7 build anyway using a Java 8 JRE. I launched my newly-installed configuration.

I added the Java 9 Support (Beta) feature from the Eclipse Marketplace. You can install it yourself by simply dragging and dropping the “Install” button below onto your Neon version of Eclipse Platform:

Drag to your running Eclipse workspace to install Java 9 Support (BETA) for Neon

The last time I tested this, I needed to have Eclipse JDT run on the Java 9 JRE to use the Java 9 support; but now, the Java 9 support seems to work just fine when running the Eclipse JDT on a Java 8 runtime. The JDT team has done some significant work, it seems, since I last looked.

I added the Java 9 JRE to the Installed JREs page in the preferences and was able to create and run a Java 9 application.


The bits that I tested all seem to work as expected; e.g. the Package Explorer lists modules.


I only spent a few minutes poking around before moving on to the next task: I wanted to get the Eclipse Platform itself running on this Java 9 build.

I tweaked the eclipse.ini file to point to the Java 9 JVM, by adding the path to the JVM at the top of the file:


I launched the Eclipse Platform and got as far as selecting the workspace before it died with a message to check the log. I opened Bug 493761. The JDT team engaged within hours. Tom Watson (from the Equinox project team) determined that a change in the boot classpath configuration is the cause and suggested as a workaround to add some additional configuration to the configuration file (after the -vmargs line) to ensure that the necessary modules are available.


For more information, see JEP 261. With that modification, everything works as expected.

The workaround is not optimal. For one, the Eclipse Platform fails to launch with this option when you launch under Java 8. The JDT team is looking for a better solution.

Your help is appreciated. If you have the time, please test this yourself and report any new information that you discover.

by waynebeaton at May 18, 2016 06:34 PM

Ecore.ecore using EcoreTools

by Cédric Brun ( at May 18, 2016 12:00 AM

A few weeks ago I ended up on the following thread on the EMF Forum asking for Ecore meta-model formal documentation?. Ed pointed at some documentation which includes diagrams done with great care but done with tools from another era.

As the maintainer of EcoreTools I had to do something about it, and so I did:

All participants in the Ecore Modeling Framework implement the EObject's interface


The following diagrams have been created thanks to EcoreTools which is part of the Eclipse Modeling Package. All the hard work has been done earlier by Ed when he had to decide what to display and how, all I did is reproduce those using EcoreTools and exporting those at a fairly high resolution (click on the images to get the full resolution).

The corresponding patchset for EMF is here.

But beside this anecdotic action there is something interesting and more general in how these diagrams are presenting the Ecore.ecore model.

Ecore Components

Ed starts by diagramming the type hierarchy, without any other information (attributes or references). And at least in the case of Ecore but in am sure it is true in the general sense, this gives a very good introduction to a domain model: only starting with the types it defines.

The Ecore components are related according to this hierarchy

To construct such a diagram using EcoreTools import all the EClasses in it and then enable the following filters:

Filters in EcoreTool

You can also enable the Constraints layer which gives a bit more information about what makes those types valid.

Layers in EcoreTool
The hiearchy + the specific constraints

Here is a general diagram highlighting the references and attributes. It might look a bit crowded at first but it is filled with information. You can get and understand how all of the primary aspects of Ecore are working just using this diagram.

The Ecore Components have the following relations, attributes, and operations

for this kind of diagrams you really want to know a few keyboard shortcuts, among others:

Hide element + ->doc
Hide label + ->doc
Remove Bendpoints + + ->doc

You’ll find all the keyboard shortcuts in Mélanie’s excellent blog post.


The next diagram focuses on how Generics are modeled in Ecore and does a fairly good job in describing it by hidding all the other aspects.

Ecore supports generics as follows

More important: this was not displayed at all in the previous diagram and that is a good thing as one don’t need to understand this specific point to leverage Ecore.

Java Language Types

The last diagrams are enumerating datatypes.

Ecore defines the data types for the following Java language types

For these kind of diagrams with many un-connected shapes your best friends are the Make same size, Distribute and Align actions.

Make same size

External Types

Ecore defines following additional data types

So now, who wants a nice poster in the office ?

Ecore.ecore using EcoreTools was originally published by Cédric Brun at CTO @ Obeo on May 18, 2016.

by Cédric Brun ( at May 18, 2016 12:00 AM

New Eclipse Download Page

by Ian Skerrett at May 17, 2016 01:53 PM

The Eclipse Board of Directors has asked the Eclipse Foundation to redesign the download page. The current download page is focused on the existing Eclipse packages and projects that are compatible with the Eclipse Platform. However, in the last number of years the Eclipse community has grown in diversity and now includes may projects that don’t necessarily fit into our packages or even the Eclipse Platform. Therefore,  the goal of a new download page is to reflect this growing diversity and showcase this diversity on our most important page.

Given this direction, we have created a draft of the new download page. The design of this new page was completed with the following objectives/assumptions:

  1. It is assumed a large majority of the visitors to the download page will be looking for technology found on the current download page. Therefore, we need to make it clear and simple for individuals that want to download the Eclipse JDT, Eclipse JavaEE tools, Eclipse CDT, etc.
  2. Our focus on installing the existing Eclipse packages is to encourage individuals to use the Eclipse Installer. It is our hope that in 12 months the current package download page will no longer be needed. The current package download page will remain the same and will be linked from this new page.
  3. We need to limit the number of options on the download page so it doesn’t become overwhelming. The goal for the new design is we don’t have more than 20 different options on the page.


As you will see the new download page has 3 main sections:

  1. Tool Platforms

Our challenge is we now have multiple platforms for creating/integrating tools. For the Eclipse Classic, our strategy is to point everyone to the Installer. For our download page, we will only promote the Installer and not individual downloads of packages or projects.

If a tool is not accessible from the Installer, we will evaluate the inclusion on the download page based on the following: 1) Project is a platform for integrating developer tools, 2) project has a download ‘tool product’ that can be used by a developer immediately after the installation. 2) project is not available as a plugin into the Eclipse Classic platform, 3) project is following the EDP :-)

  1. Runtime Platforms

We have a number of projects that are not tools but application/runtime platforms for running applications. A Runtime Platform will be defined as a project that includes a runtime container, like Eclipse Jetty, Eclipse Equinox, etc.

  1. Technology Communities

It is important we promote our Working Groups and other technology communities within Eclipse. Working Groups are a critical part of the Foundation strategy so we need to include them on our highest traffic web page. For Working Groups or communities to be included, they will need to have a maintained download page with at least 3 different downloads that include 3 different Eclipse projects and following the EDP.

I think the new page looks great. It is modern, simple and achieves all the goals. Thanks for Eric, Kat, Matt and everyone else at the Foundation for doing a great job.

Let us know what you think. Please leave your feedback on this bug.

by Ian Skerrett at May 17, 2016 01:53 PM

Last Chance to Register for EclipseCon France 2016!

May 17, 2016 05:10 AM

Presenting new stand alone sessions, more workshops, and unparalleled conference value, it's not too late to register!

May 17, 2016 05:10 AM

Network Dynamics and Micro Services

by Scott Lewis ( at May 16, 2016 08:22 PM

One of the most challenging aspects of building networked applications is dealing with network dynamics. Networks and endpoints go down, sometimes come back up, and this implies that consumers accessing these services have to respond as these changes occur.

This will be even more true for the Internet of Things (IoT), where a wide variety of devices and a wide variety of networks will be involved to support the use of a micro service. Through no design or programming fault, IoT services and the applications that depend upon them will be less reliable.

How should micro-service consumers respond to failure? That's a good question, as the answer clearly depends upon the application-level needs and requirements.

For example, once loaded an html web page does not need to know/respond to the failure of the web server or the dropping (or changing due to mobility) of the network connecting the browser to the web server. If the user clicks on a link to present another page the load of the page will fail, but for browsing web pages that's a completely acceptable strategy for handling network failure.

On the other hand, consider an IoT application where a real-time data stream is collected from a sensor device. In such a case it might make more sense to have strategy for responding to network and/or device failure such as switching to a backup, or perhaps presenting to a user or admin that the data stream is temporarily unavailable. The larger point is that consumers of a micro service will differ in their requirements for responding to network failures.

What does any of this have to do with micro services? Frequently it falls to the application to not only define a strategy for application-level failure handling, but also to implement the networking code to detect failure and to use this detection to allow an application to implement a failure-handling strategy. This networking code can be a very difficult thing to create, especially if it has to meet multiple service and application-level requirements.

There are now specifications allowing the excellent dynamics support in OSGi Services to be used for Remote Services. The OSGi Service Registry, was designed to support dynamic within-process services. This allows applications to respond to services that come and go dynamically without having to create all the software infrastructure to do so reliably. Further, there are now OSGi specifications for Remote Services, and these allow the same dynamics support to be used to respond to network dynamics. Since the OSGi service registry is standardized, applications can also use (rather than build) convenient frameworks like Declarative Services/SCR or Spring/Blueprint to respond to network-induced service changes.

In short, the OSGi service registry and Remote Services provide standardized support for micro services dynamics without being bound by implementation to a specific protocol/transport, or even language.

by Scott Lewis ( at May 16, 2016 08:22 PM

Git Staging View

by waynebeaton at May 16, 2016 07:57 PM

I’ll admit that I never bothered much with the Git Staging View before now, preferring instead to make all of my commits from the Commit dialog.

The milestone seven (M7) builds of the Neon versions of the various Eclipse IDE downloads now all bring the Git Staging view to the top instead of opening the Commit dialog when you invoke the “Commit…” command.

Screenshot from 2016-05-16 15-33-08

This is configurable in the preferences (on by default).

Screenshot from 2016-05-16 15-46-51

Using the view requires a bit of a change in my habits, and so it will probably take a few iterations before it starts to get comfortable, but it’s a change that I think is worth making: probably every other time I open the Commit dialog, I have to close it to go and copy some bits of a comment that I want to put into the commit message, before opening it again. The non-blocking nature of views makes this problem go away.

Dragging and dropping between unstaged and staged changes is also darned handy.

The Eclipse Neon Simultaneous Release is scheduled for June 22/2016. Milestone (developer) builds of the Eclipse IDEs for this release are now available as Developer Builds on the Eclipse download site.

by waynebeaton at May 16, 2016 07:57 PM

5 Things I Learnt at IoT World 2016

by Benjamin Cabé at May 16, 2016 01:19 PM

Last week I attended IoT World in Santa Clara. It was a great event, and what was particularly exciting was to meet with adopters of Eclipse IoT technology who stopped by our booth. It just felt incredibly energizing (and even more so given I had to spend 2.5 hours at US immigration the day before the show, which was quite annoying, to say the least).

Here are 5 things I learnt at IoT World, and that I thought I would share with you:

→ Eclipse Wakaama and Eclipse Leshan are saving lives

thingwaveThat tweet I reshared just above was done right after a discussion I had with Jens Eliasson from Thingwave. Thingwave is a company that is building a connected device that aims at monitoring vibration in rock bolts used in the mining industry, in order to detect anomalies such as excessive strain.

Their solution, called the Smart Rock Bolt, is attached directly to a bolt (see picture) and uses LWM2M (thanks to open source implementations Eclipse Wakaama and Eclipse Leshan) and IPSO Smart Objects to expose sensor data that a gateway collects and analyzes.

You can read more on the Smart rock bolt on Ericsson Research blog.

→ MQTT remains an IoT protocol of choice

mqttorgIt was only one hour or so before the end of IoT World that my colleague Ian and I found out that just next to our booth was a company, infiswift, building an IoT platform around a highly-scalable MQTT broker. But in fact, it is no surprise, since pretty much every person we met, and many of the companies exhibiting, were either building solutions using MQTT or already very much aware of its capabilities. So we should have just guessed about infiswift :-)

→ Eclipse IoT technology to be shipped with a Kickstarter project that raised $1.7M


Pine 64 is a Raspberry Pi-like single board computer which aims to be a very affordable 64-bit computing solution, with a price tag starting at just $15.

I met Daniel Kottke, one of the persons involved with the Pine 64 project (and employee #12 at Apple, where he participated to the H/W design of the Apple I), and this is from him that I learnt about the project and its incredibly successful Kickstarter campaign. What I found really exciting is that Pine 64, in its “IoT Package” version, will ship with openHAB pre-loaded on its SD card. And as you probably know, openHAB is running on top of the very popular Eclipse IoT project Eclipse SmartHome.


→ Eclipse Kura becoming a framework of choice for building IoT gateways

kuraFrom Litmus Automation, to Eurotech, to the likes of Microsoft or Cisco now looking at Eclipse Kura, it was great to see that many companies are endorsing it as a framework of choice for building modular and extensible IoT gateways.

All in all, it was a very good conference. I am looking forward to next year’s edition and to see how the IoT industry will have evolved by then. This year it was already pretty clear that the consumer IoT market is starting to consolidate, and that everyone’s attention is shifting towards Industrial IoT (as an example, this year’s hackathon was sponsored by GE) .

By the way, from one conference to the other: this week I am in Austin for OSCON’16. If you are attending, please stop by Eclipse Foundation booth to say hello!

by Benjamin Cabé at May 16, 2016 01:19 PM

Using Hi-DPI icons in Eclipse Neon M7

by Torkild at May 15, 2016 07:19 PM

EclipseCon France is taking place in a few weeks so I figured it’s about time I started working on my presentation and get distracted doing so. This year I’m talking about How Mylyn Docs can be a powerful tool. For the EclipseCon North America version of this talk I wrote a very basic LaTeX equation editor to show how you can easily integrate mathematical expressions into your PDF or EPUB using the Mylyn Docs API with a few extras. It has content assist and shows an icon illustrating the macro to the left of the text, as most of these implementations in Eclipse. Now rendering a more advanced mathematical operator or greek letter in 16×16 pixels just makes it look horrible, so I’ve been waiting for the day when I can use high(er) resolution images. That was only one of the reasons it was slightly embarrassing demonstrating that editor.

Support for high-DPI displays in Eclipse has been in the works for about four years. For those of us on a “retina” MacBook, the lack of it has not been much of a problem since fonts could be fixed with a simple setting and images are automatically scaled. Images appeared blurred, but that was it. However on Windows and Linux icons have been tiny, making Eclipse practically useless in some configurations.

Since Eclipse 4.6 milestone 6, presentation on high DPI monitors has improved. Images are now automatically scaled to the correct size also on Windows and Linux. The one bit that is missing is providing support for higher resolution icons, typically at 2x and 1.5x. I went digging through bug reports and code to see how this can be done. The bad news is that it’s not yet quite in place, the good news is that you can get it to work, and I guess it will be ready by the Neon release. There were a few bits that caught my attention:

  • The zoom level currently used by the operating system is exposed through the system property org.eclipse.swt.internal.deviceZoom. You should not have to care about that.
  • There is a SWT snippet for testing use of DPI-aware image constructors at the usual location.
  • There is a debug option to enable high-DPI images via the “@2x” filename convention. Yummy!

I’m really happy that the team behind the implementation chose this approach. It makes it so easy to add the new images and it does not break backwards compatibility. So I changed my target platform to use 4.6M7 and did some minor changes to the code in addition to generating the higher DPI image files. I used ImageDescriptor imageDescriptor = ImageDescriptor.createFromURL(url) to create the ImageDescriptor for each icon, as it appears that this is (only) the way to go. Earlier I was using the file path. That way the mechanism that detects the “@2x” suffix will be activated and the icon will be “magically” rendered correctly. I also added some debug options to my launch configuration to enable it:


Notice that in the screenshot above, the editor icon is also rendered in the 2x version. It was simply a matter of adding a new image in double the size with the “@2x” suffix. So we have icon.png, icon@1.5x.png and icon@2x.png.

For reference here is the 1x version:


I don’t know when we can officially use this feature and I am jumping the gun, but I think we should get started already and prepare our plug-ins. High DPI displays are here to stay. Thanks to everyone that has been working on this, you guys are awesome! I’m certainly looking forward to using Eclipse with beautifully rendered @2x-icons 😄

Oh, and if you want to learn about how to easily generate PDFs, EPUBs and more, including equations, using the Mylyn Docs API, meet me at EclipseCon France. And for those interested in the equation writer; there is a decent preview, utilizing MathJax for the LaTeX rendering.


by Torkild at May 15, 2016 07:19 PM

Presentation: Creating a Complex Form-Based UI in 30 Minutes

by Maximilian Koegel at May 14, 2016 01:09 AM

Maximilian Koegel demos the creation of an EMF form defining the underlying data entity, tables for referenced entities, validations, conditions, and embedding the form into a running application.

By Maximilian Koegel

by Maximilian Koegel at May 14, 2016 01:09 AM

Presentation: Integrating Different IDEs with a Common Set of Developer Services

by David Staheli at May 13, 2016 11:43 PM

David Staheli discusses approaches Microsoft is taking to plugin development, sharing experiences in reusing code across plugins for different IDEs, with demos of plugins in Eclipse, IntelliJ, and VS.

By David Staheli

by David Staheli at May 13, 2016 11:43 PM

Boost Productivity with MyEclipse—Coding & Navigation

by Srivatsan Sundararajan at May 13, 2016 07:59 PM

MyEclipse is a powerful Java EE IDE for today’s modern enterprise developer. This article is the second in a series discussing ways to boost productivity with MyEclipse. The first article, focused on project setup. This article showcases time-saving tips and tricks to improve MyEclipse coding and navigation.Code CompletionMyEclipse delivers an intelligent and robust content assist engine that […]

The post Boost Productivity with MyEclipse—Coding & Navigation appeared first on Genuitec.

by Srivatsan Sundararajan at May 13, 2016 07:59 PM

Great Fixes from Till Brychcy

by waynebeaton at May 13, 2016 06:28 PM

Our third winner in the Great Fixes for Neon skills competition is Till Brychcy.

Till has used the Eclipse Java development tools (JDT) since 2003, and made his first contribution in 2013. In the time between the 2015 Mars release and today, Till has had 41 separate commits accepted by the JDT project team—most of which provide improvements in the null analysis support—adding almost 20K net new lines of code.

Till quite likes the annotation based null analysis that was introduced with Eclipse JDT 3.8 and is looking forward to Substring code completion and the problem decorator for Info severity introduced in the M5 Neon milestone builds.


The Great Fixes Candidates page shows a list of the commits attributed to Till, along with those of the other Great Fix candidates.

Eclipse Neon is on track to be released into the world on June 22/2016. But you can download and test out the latest milestone builds today.

Edit: Till has been invited to join the JDT team as a committer.

by waynebeaton at May 13, 2016 06:28 PM