Eclipse Neon: 5:30-minute demo of 22 nice improvements

by howlger at June 26, 2016 04:31 PM

Watch a 5:30-minute demo of 22 nice Eclipse Neon improvements, including IDE, Java and Web/JavaScript:

Eclipse Neon: 5:30-minute demo of 22 nice improvements

For more details there are 4:34:25 hours of Eclipse Neon Webinars.



by howlger at June 26, 2016 04:31 PM

Solve weird java.io.EOFException at java.io.DataInputStream.readFully in Oomph with Eclipse Neon

by Michael Vorburger (noreply@blogger.com) at June 26, 2016 07:35 AM

If you are getting the first error (1) below when using an Eclipse Installer (Oomph) v2441, then just re-download a fresh later version from https://www.eclipse.org/downloads/ (e.g. 2444 at the time of writing), and it will work again.  For some reason, the Auto Update does not work to get from Oomph 2441 to 2444.

If you are then still getting the second error (2) below, after having upgraded Oomph, then simply retry by restarting Oomph or even simply by using the <Back and Next> and this appears to go away.  Alternatively, perhaps you would like to blow away your entire p2 cache via rm -rf ~/.p2 (although normally this should not be required).


(1) Fetching content.xml.xz from http://download.eclipse.org/technology/epp/packages/neon/
ERROR: org.eclipse.equinox.p2.metadata.repository code=1002 Unable to read repository at http://download.eclipse.org/technology/epp/packages/neon.
java.io.EOFException
  at java.io.DataInputStream.readFully(DataInputStream.java:197)
  at java.io.DataInputStream.readFully(DataInputStream.java:169)
  at org.tukaani.xz.SingleXZInputStream.initialize(Unknown Source)
  at org.tukaani.xz.SingleXZInputStream.<init>(Unknown Source)
  at org.tukaani.xz.XZInputStream.<init>(Unknown Source)
  at org.tukaani.xz.XZInputStream.<init>(Unknown Source)
  at org.eclipse.equinox.internal.p2.metadata.repository.XZedSimpleMetadataRepositoryFactory.load(XZedSimpleMetadataRepositoryFactory.java:80)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
  at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
  at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
  at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:370)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:177)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:437)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
  at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl$RepositoryLoader$Worker.perform(ProfileTransactionImpl.java:1625)
  at org.eclipse.oomph.util.WorkerPool$Worker.run(WorkerPool.java:416)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)


(2) ERROR: org.eclipse.equinox.p2.metadata.repository code=1002 Unable to read repository at http://download.eclipse.org/releases/neon.
ERROR: org.eclipse.equinox.p2.repository code=0 An error occurred while downloading http://download.eclipse.org/technology/epp/packages/neon/content.xml.xz. The cache file /home/vorburger/.p2/org.eclipse.equinox.p2.repository/cache/downloading/2079680757 could not be renamed to /home/vorburger/.p2/org.eclipse.equinox.p2.repository/cache/2079680757.
  at org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:428)
  at org.eclipse.equinox.internal.p2.repository.CacheManager.createCacheFromFile(CacheManager.java:132)
  at org.eclipse.equinox.internal.p2.metadata.repository.XZedSimpleMetadataRepositoryFactory.getLocalFile(XZedSimpleMetadataRepositoryFactory.java:56)
  at org.eclipse.equinox.internal.p2.metadata.repository.XZedSimpleMetadataRepositoryFactory.load(XZedSimpleMetadataRepositoryFactory.java:78)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
  at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
  at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
  at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:370)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:177)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:437)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
  at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
  at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
  at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
  at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
  at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
  at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:370)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:177)
  at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:437)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
  at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
  at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl$RepositoryLoader$Worker.perform(ProfileTransactionImpl.java:1625)
  at org.eclipse.oomph.util.WorkerPool$Worker.run(WorkerPool.java:416)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

by Michael Vorburger (noreply@blogger.com) at June 26, 2016 07:35 AM

Boost Eclipse Neon JavaScript Development with JSjet

by Brian Fernandes at June 24, 2016 02:14 PM

While far from an expert, I’ve been working with JavaScript for ages. I started off using JavaScript for DHTML (anyone remember that term?) when cross-browser meant your site would work with Internet Explorer and Netscape Navigator. I moved on to using JavaScript for desktop widgets and finally, browser extensions for Firefox and Chrome. A big […]

The post Boost Eclipse Neon JavaScript Development with JSjet appeared first on Genuitec.


by Brian Fernandes at June 24, 2016 02:14 PM

Eclipse Webinar series - JSDT and Docker Tooling for Eclipse Neon

by xcoulon at June 24, 2016 10:23 AM

To celebrate the release of Eclipse Neon, the Eclipse Foundation produced a webinar series with a list of 7 of the Top New & Noteworthy Features that are integral to the Eclipse Neon Release.

Amongst those webinars, Ilya and Gorkem presented the Eclipse JavaScript Development Tools (JSDT) and I presented the Docker tooling.

JSDT Tooling

Description:

The Eclipse JavaScript Development Tools have reached a new level of features and usability with Eclipse Neon. Many things were implemented as part of the JSDT 2.0 release that is now available with Eclipse Neon. This webinar demonstrates the following new features:

  • Package managers (npm / bower)

  • Build systems (grunt / gulp)

  • Node.js Tools

  • ECMAScript 2015 (ES6) parser

The talk also features plans for the future of JavaScript development in Eclipse IDE.

The slides for the presentation are available here.

Docker Tooling

Description:

Docker is awesome, but how to use it well when doing development? In this talk you will get a quick introduction on how to use Docker effectively, especially for development from within Eclipse. We will show how the release of Eclipse Neon supports Docker to make it even more integrated into your day-to-day work from within your IDE. In particular, you’ll see how you can pull and run an image for a database, build a custom image for an application server, run it and deploy an application using data volume, exposed ports and container links. We will also take a look at some of the newest features, such as support for Docker Machine, TM Terminal integration, run configurations for containers, and a variety of other UI improvements.

The slides for the presentation are available here.

Other Webinars

Other webinars have also been recorded and are available on the Eclipse Neon Webinar Series on Youtube.

Enjoy !
Xavier Coulon
@xcoulon


by xcoulon at June 24, 2016 10:23 AM

Eclipse Newsletter - Eclipse Neon Shines Bright

June 23, 2016 02:00 PM

Read about the top ten Neon features, the new Eclipse User Storage Service (USS), Eclipse CDT 9.0, and Eclipse PDT 4.0.

June 23, 2016 02:00 PM

New Eclipse Neon Packages for JavaScript and Android

by ignaciom at June 23, 2016 01:24 PM

Eclipse Neon Android Package Now that Eclipse Neon is just around the corner, I was pleased to see that Eclipse for Android Developers is back. We’ve all waited a long time for it! This package bundles the Andmore-Eclipse Android Tooling—a fork of Google’s ADT (Android Development Tools) plugins for Eclipse. These are maintained separately from […]

The post New Eclipse Neon Packages for JavaScript and Android appeared first on Genuitec.


by ignaciom at June 23, 2016 01:24 PM

Eclipse Neon and ssh-agent

by Gunnar Wagenknecht at June 23, 2016 12:31 PM

Eclipse Neon is out. Time to give a long awaited feature a try again. It’s support for re-using the identify from ssh-agent running on my system within Eclipse. I want this primarily for the Eclipse Git integration.

As it turns out, the core support is part of Eclipse Neon. The SSH interface had been made extensible for additional identity discovery. The remaining missing piece is the actual code that bridges the ssh-agent connection into the Eclipse SSH interface (powered by JSch). The reason for this are – of course – legal issues. It would be great if those can be addressed and this can be shipped out of the box in Eclipse.

I forked the initial work from the JSch folks and made it consumable as an update site.

Please give it a try:
https://eclipseguru.github.io/eclipse-jsch-agent-proxy/


by Gunnar Wagenknecht at June 23, 2016 12:31 PM

Clean Sheet Update for Eclipse Neon

by Frank Appel at June 23, 2016 05:37 AM

Written by Frank Appel

In celebration of the latest Eclipse release, we provide a Clean Sheet Update for Eclipse Neon. Congratulations and a big ‘thank you’ to all the diligent Eclipse committers and contributors that made the Neon version happen, great work! While the Clean Sheet Update for Eclipse Neon primarily ensures compatibility it comes also with some nice Look-and-Feel improvements. This post gives a short overview of the most important innovations of the feature’s new version (0.4).

 

The Clean Sheet Eclipse Design

In case you've missed out on the topic and you are wondering what I'm talking about, here is a screenshot of my real world setup using the Clean Sheet theme (click on the image to enlarge). Eclipse IDE Look and Feel: Clean Sheet Screenshot For more information please refer to the features landing page at http://fappel.github.io/xiliary/clean-sheet.html, read the introductory Clean Sheet feature description blog post, and check out the New & Noteworthy page.

 

FlatScrollBar Overlay for ScrolledComposite

Styling capabilities have been enhanced to allow adoption of ScrolledComposite widgets and derivatives by the FlatScrollBar overlay mechanism on Windows platforms. The picture shows how the content area of the preference dialog blends in the Clean Sheet scrollbars on diminution.

Clean Sheet Update for Eclipse Neon: Scrolled Composite Overlay

Forms Style Adjustment

The styling of FormToolkit based views and editors has been overhauled. Together with the FlatScrollBar overlay mechanism on ScrolledForms (Windows only), UI parts like the PDE Manifest editor integrate now quite nicely with the overall look and feel of the Clean Sheet theme.

Clean Sheet Update for Eclipse Neon: Forms Look and Feel

Clean Sheet Installation

Drag the 'Install' link below to your running Eclipse instance

Drag to your running Eclipse installation to install Clean Sheet

or

Select Help > Install New Software.../Check for Updates.
P2 repository software site: @ http://fappel.github.io/xiliary/
Feature: Code Affine Theme

After feature installation and workbench restart select the ‘Clean Sheet’ theme:
Preferences: General > Appearance > Theme: Clean Sheet

 

On a Final Note, …

Of course, it’s interesting to hear suggestions or find out about potential issues that need to be resolved. In particular, as the ScrolledComposite widget has some interesting layout mechanisms by itself there still might be some uncovered spots with the newly added scrollbar overlay mechanism. Feel free to use the Xiliary Issue Tracker or the comment section below for reporting.

With this in mind, I’d like to thank all adopters for the support and hope that everybody likes the Clean Sheet Update for Eclipse Neon as much as we do 😉

The post Clean Sheet Update for Eclipse Neon appeared first on Code Affine.


by Frank Appel at June 23, 2016 05:37 AM

Eclipse Marketplace: Neon and 20 Million

by Ian Skerrett at June 22, 2016 07:40 PM

The Eclipse Neon release is now out. I also noticed Eclipse Marketplace just passed the 20 million successful install milestone. Wow, that is a lot of developers using Eclipse Marketplace.

Eclipse Marketplace - 20 million

For the Neon release, there are two key features that I think will accelerate the use of Eclipse Marketplace Client (MPC).

  1. Eclipse MPC now allows you to store your Favorite with your Eclipse account. The other very cool feature is you can import someone else favorite list. Here is my favorite list if you are to give it a try.

mpc favorites

2. In Eclipse Neon, selecting the text editor for associated file types now allows a user to search Eclipse Marketplace Client for plug-ins that support that file type. This should make it a lot easier for developers to find the appropriate plug-in from Eclipse Marketplace.

Congratulations to everyone that made the Eclipse Neon release possible. Another great community collaboration.

 



by Ian Skerrett at June 22, 2016 07:40 PM

New and noteworthy for codeEdit widget 12

by Libing Wang at June 22, 2016 06:25 PM

Orion codeEdit widget debuted just one year ago in Orion 9.0. Thanks to all the valuable user feedback over the past year, now in Orion 12, the widget has been improved a lot for both usability and customizability. We’ve updated the widget wiki page to include the latest features, summarizing user feedback in the FAQ section.

The codeEdit demo page shows you two of the biggest improvements in the widget: customizable editor configurations and fine tuning your web language tooling. In Orion 11.0 we introduced tern project – now this feature is integrated into the widget. In the demo you will see a zoom ruler in each editor, enabled by an editor configuration change. You will also see how the javascript file validation behavior changes while live editing the tern project and eslint rule files.

Aside from that, there are other major improvements that are not shown in the demo.

With all the improvements so far, we found it’s been much easier for the existing users to consume and customize the widget. We are still improving in other areas so please stay tuned.


by Libing Wang at June 22, 2016 06:25 PM

New and Noteworthy in Javascript tooling for Orion 12.0

by Olivier Thomann at June 22, 2016 05:15 PM

As noted in our Orion 12.0 announcement, a tonne of work has gone into this release of Orion.  Over 350 Bugzilla reports were fixed.  Here are some of the many things we have been working on for the JavaScript language tooling.  Expect more in-depth looks at these items in the next few weeks.

Cross-file linting

The ESLint based validation in our JavaScript tools up to Orion 11 was only focused on the single file you were editing.  No consideration was given to the rest of your project setup.  With 12.0 the linting is now aware of the other files in your workspace and the project configuration you have set up.

  • no-undef: Warn when a global variable has not been defined
  • no-undef-expression:  Warn when a function (member expression) has not been defined
  • no-unused-vars: Warn when declared variables are not used.
  • unknown-require:  Unknown required library
  • type-checked-consistent-return: Discouraged inconsistent returns

So we can now in many cases tell you that you are using a function that doesn’t exist.  Especially helpful when you mistype the name or use the wrong casing.

Make the tools consumable

We have created a new API and webpack build that will package up the JavaScript tooling in one consumable bundle that can be used to drive language plugins for other IDEs, such as Brackets or Atom.

A deep-dive into the new API is coming in a subsequent blog post. To get a jump on it, we have provided two wiki pages: (1) JavaScript tools API and, (2) Building the JavaScript API.

Improved Tern integration

In Orion 12.0 we moved the remainder of our client-side services to be Tern plugins.

These new plugins include:

  1. ESlint
  2. Occurrences
  3. Templates / templating
  4. Quickfixes
  5. Outlining

The move to be more Tern-centric with our features carries many benefits, but most importantly it allows us to cut down on message passing, improve memory use and make the features more portable.

ECMA 2015 support

Orion 12.0 supports all of the ECMA 2015 specification like arrow functions, import/export statements and classes.

The tooling completely understands the new language syntax with new quick fixes and code templates also being available to get you started.  The linting rules have also been updated to respect the new ECMA 2015 code patterns.

Outlining has been updated:

ECMA 2015 outlining support

ECMA 2015 outlining support

Occurrences has been updated:

ECMA 2015 occurrences support

ECMA 2015 occurrences support

Linting has been updated:

Lint rules updated for ECMA 2015

Lint rules updated for ECMA 2015

We also support import and export statements which require the source type to be “module”. This is set through the .tern-project file – and you can use a handy quickfix to write it all for you.

Change sourceType quickfix

Change sourceType quickfix

Support for ESLint project configuration files

Users can now include .eslintrc files in their projects.  These files can configure all of the ESLint settings that your files are validated with, including rule severities.

.eslintrc file example

.eslintrc file example

When this file is present, the rule values will override any workspace settings.  If you go from editing your project to changing settings the page will warn you that an .eslintrc file is present.

Preference warning banner for .eslintrc overrides

Preference warning banner for .eslintrc overrides

We support other forms of ESLint configuration too, such as settings in package.json. There is a hierarchy of configuration files that you can use. Read the full details on ESLint’s configuration page.

Package.json ESlint configuration section

Package.json ESlint configuration section

Support for in-project definition files

You can define and use your own definition files in your project. See the file IndexCreation.md to find out how to proceed.

Tern index file example

Tern index file example

The tooling will include all the type information found in your definitions to improve content assist, tooltip hovers and more.

Content assist for example in-project index file

Content assist for example in-project index file

Updated third-party libraries

Most of our third-party libraries have been refreshed:

  • Acorn 3.1.0
  • Doctrine 1.2.1
  • ESrecurse 4.1.0
  • Estraverse 4.1.1
  • Escope 4.2.0
  • Tern 0.18.0

A notable change to our consumed library lineup is that we have discontinued use of the Esprima parser in favour of Acorn.  There are many reasons for the switch, but the main reasons are:

  • Acorn has complete ECMA 2015 support (with recovery for most of it).
  • We can easily extend the Acorn parser via its plugin mechanism, so there is no need to edit parser code to have our Orion customizations.
  • Acorn has robust recovery support right out of the box (no more editing the parser to hack our own in).

by Olivier Thomann at June 22, 2016 05:15 PM

Announcing Handly 0.5

by Vladimir Piskarev at June 22, 2016 05:00 PM

I am very pleased to announce the availability of the Handly 0.5 release, a true “2.0” version in spirit. This release introduces an entirely new design that gives the implementor of a Handly-based model complete control over the model API. Among other things, this should make it possible to use Handly for (re-)implementing handle-based models where the model API is a given, just as in the case of a preexisting model API that needs to be preserved for backward compatibility. Many of the core APIs have been revised in this release to make Handly even more flexible and robust.

New and Noteworthy
Migration Guide
Downloads

Any feedback would be greatly appreciated.

Many thanks to all who contributed to this release:

  • Ondrej Ilcik, head of IDE Team at Codasip, has kindly contributed a navigator view for the Java model example, which made its way into this release. This is the first significant (~ 4K LOC) contribution to the project by a non-committer. Codasip Studio is one of the earliest adopters of Handly, and it is really great to see that a major adopter becomes a significant contributor. Also, Ondrej has been so kind as to share a great success story of Codasip Studio and Handly, which is all the more valuable as the first success story published by a Handly adopter.
  • Vlad Dumitrescu, the project lead of erlide, has been actively participating in discussions on the project’s mailing list. His earlier feedback helped inspire the new design introduced in this release, and he has also contributed great ideas about restructuring the project’s web page to make it more readable.
  • Peter Gribanov, 1C, has contributed a success story describing how 1C:Enterprise Development Tools, the earliest adopter of the project, is using Handly.

Thank you for contributing!


by Vladimir Piskarev at June 22, 2016 05:00 PM

GEF4 Dot Oh Dot Oh

by Alexander Nyßen (noreply@blogger.com) at June 22, 2016 03:33 PM

I am proud to announce that with today's Eclipse Neon release we have officially published the new GEF4 components in version 1.0.0, exposing their up to now only preliminary API. We have worked intensively on the code base since the 0.2.0 (Mars.1) release and have achieved quite a lot.

Polishing API

From an adopters viewpoint, the (up to now provisional) API has been cleaned up and harmonized in nearly all places. We have for instance adopted JavaFX collections and properties throughout, so that we can now use only a single notification mechanism in all places. As outlined in detail in an earlier post, this also enables us to use JavaFX bindings, which makes framework and client code more concise. Especially the GEF4 FX component has profited a lot from this. We have further simplified the contract of the GEF4 Layout component to no longer rely on own interface abstractions for data exchange, but to use a GEF4 Graph model, similar to what GEF4 Zest already did for rendering. And we have harmonized the GEF4 Zest API, especially those parts related to JFace. The New and Noteworthy page gives a quite detailed overview of the most important API changes.

Improving DOT

From an end-users viewpoint, the GEF4 DOT component has been brought a huge step nearer to its final goal of being a full Graphviz DOT authoring environment (even if its still a far way to go). The Xtext editor can now also parse and validate certain attribute values, and the Graph view is capable of rendering a first set of node shapes, as well as edge styles and decorations. All DOT spline types are now also supported. In addition to the 'emulated' layout we provided so far, where a GEF4 Layout algorithm is used to mimic the Graphviz layout, we now support a 'native' mode, in which the native dot executable (the path to which is specified via a preference) is used:

















'Pimping' FX and MVC

Connection handling has been significantly improved. We have added support for orthogonal routing in addition to straight routing, and we have separated out an IConnectionRouter, which is responsible for manipulating the bend/control points, as well as an IConnectionInterpolator, which determines the to be rendered curve geometry. Routers and interpolators can be freely combined, so a connection can now be routed orthogonally, while it can still be rendered ‚smoothly‘ using Bézier curves:



















In addition, connection decorations are now properly clipped (which lies within the responsibility of the interpolator), and a 'clickable area‘ (a transparent fat curve that overlays the connection) can now be used to make a connection clickable even when the zoom level is large (we have added this functionality to the GeometryNode so it is usable in an even broader scope).

Within GEF4 MVC we have accordingly enhanced FXBendConnectionPolicy to provide interaction support for manipulating connections that are orthogonally routed. These can now be manipulated using segment handles rather than handles for way/control points:


We have further enabled that distinct bindings can be specified for viewers with different roles. That allows us to use an FXViewer both as palette and content viewer, so a palette can now be easily realized. We have augmented the MVC Logo example to serve as a demonstrator:



by Alexander Nyßen (noreply@blogger.com) at June 22, 2016 03:33 PM

Announcing Orion 12

by Mike Rennie at June 22, 2016 03:27 PM

We are pleased to announce the twelfth release of Orion, “Your IDE in the Cloud”. You can run it now on OrionHub or download the server to run your own instance. Once again, thank you to all committers and contributors for your hard work this release.  There were over 350 bugs and enhancements fixed, across more than 900 commits from 22 authors!

What’s new in Orion 12?  The Orion 12 release continues to emphasize our JavaScript tooling.  In particular, we now have full support for the ECMA 2015 spec, vastly improved project configuration capabilities, support for eslintrc.* files and much much more!

The other focus of this release is consumability. To make Orion easier to use for end users, admins and everyone in between, we created an experimental node.js server (which can be used on orion.eclipse.org or locally), a metrics service for plugins, some super cool updates to the code edit widget and a whole lot more!

Enjoy!


by Mike Rennie at June 22, 2016 03:27 PM

WTP 3.8 Released!

June 22, 2016 03:14 PM

The Eclipse Web Tools Platform 3.8 (Neon) has been released! Featured in the Eclipse IDE for Java EE Developers, you'll also find parts of WTP in many of the Neon packages. Of course you can still download the raw WTP 3.8 build manually--don't forget the dependencies if you do. Anyone with a working Eclipse 4.6, or Neon package, can install WTP by working with the Neon and corresponding WTP Update Sites.

More news


June 22, 2016 03:14 PM

Eclipse Foundation Releases Neon

by Alex Blewitt at June 22, 2016 02:00 PM

Today, the Eclipse Foundation announced the release of Eclipse Neon, the eponymous IDE which provides support for Java, JavaScript, C/C++, PHP and Fortran, amongst others. This release marks the eleventh release of the combined release train, with contributions from 779 developers (of which 331 are committers) and totalling 69 million lines of code. Read on to find out what's new in this release.

By Alex Blewitt

by Alex Blewitt at June 22, 2016 02:00 PM

Eclipse Neon Release Train Now Available

June 22, 2016 02:00 PM

We're proud to announce the availability of the Neon release, the annual release train from the Eclipse community.

June 22, 2016 02:00 PM

Eclipse Neon Java Editor Gets More Awesomeness

by aaronlonin at June 22, 2016 01:10 PM

I always appreciate those “small things” that help me write better code and code faster. Eclipse Neon comes with a great set of those small things right in the Java editor. As a Java developer I can’t help but feel excited about the new features Neon has and how it has a better integration with […]

The post Eclipse Neon Java Editor Gets More Awesomeness appeared first on Genuitec.


by aaronlonin at June 22, 2016 01:10 PM

Sirius 4.0 Gotta Catch ‘Em All: Fully operational battle station!

by Melanie Bats at June 22, 2016 07:00 AM

Finally, with Sirius 4.0, some newly introduced components are declared fully operational.

Compartments

Sirius 3.1 came with the possibility to create compartments where you can group and stack your model elements. The way your data is represented is better structured and the information is easier to understand. With Sirius 3.0, it was already possible to create compartments, but we had introduced it as an “experimental” feature since some behaviors were not supported yet. Today compartments are fully operational.

I18N

We completed our work on the internationalization. Now the runtime strings are externalized and a dedicated mechanism exists for the odesign files.
 To catch all the new features coming with Sirius 4.0 have a look to the slides of our talk at EclipseCon France! Another chance for you to join the Sirius community, SiriusCon will occur in Paris the 15th November 2016. Be sure to save the date!


by Melanie Bats at June 22, 2016 07:00 AM

Open Container Initiative at 12 Months

by Chris Aniszczyk at June 21, 2016 05:34 PM

Today at DockerCon 2016 I had fun speaking with colleagues on where we are with the Open Container Initiative (OCI) after about a year:

OCI

The industry needs standards around the container format/runtime to enable portability, if you’re interested in joining this effort you can find more information here: https://www.opencontainers.org/join


by Chris Aniszczyk at June 21, 2016 05:34 PM