Eclipse e(fx)clipse™ 2.1.0 Release Review

Type
Release
State
Successful
End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Project
Eclipse e(fx)clipse™
Release

2.1.0

Description

Once more the main focus in this release was put on runtime components.

The most significant addition was a new provisional components allowing developers to build Code editor with a mixture of e(fx)clipse, Eclipse Text and a dedicated DSL. As a starting point we published a set of blog posts:

In the tooling space we fixed all bug reports we received the new error reporting tool provided by the Eclipse installations.

API Certification

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues

This is a minor release without any changes to the overall architecture.

Generally the runtime components aim to get more and more aligned to the pure OSGi-Specification by not using Eclipse specific stuff anymore (eg we don't use Extension Points but wire stuff using DS-Service)

Non-Code Aspects

We are making available those new components are provisional APIs:

  • org.eclipse.fx.code.editor: Core APIs required to build and editor
  • org.eclipse.fx.code.editor.e4: Eclipse 4 specific Core implementations to build a smart editor
  • org.eclipse.fx.code.editor.fx: JavaFX specific APIs to build an editor
  • org.eclipse.fx.code.editor.fx.e4: JavaFX and e4 specific implementations to build an smart editor
  • org.eclipse.fx.code.editor.fx.themes: Themes for the editor
  • org.eclipse.fx.code.editor.ldef: DSL to setup editors
  • org.eclipse.fx.code.editor.ldef.langs: Language definitions for Java, JavaScript, Dart, ....
  • org.eclipse.fx.code.editor.ldef.text: Components to setup an editor directly from the ldef specification instead of code
  • org.eclipse.fx.code.editor.ldef.text.fx: JavaFX components to setup an editor directly from the ldef specification instead of code
  • org.eclipse.fx.code.outline: APIs to define build and outline
  • org.eclipse.fx.code.outline.e4: Simple integration of an outline in e4
  • org.eclipse.fx.text: Extractions from org.eclipse.jface.text who are UI-Toolkit independent
  • org.eclipse.fx.text.ui: Components from org.eclipse.jface.text ported to JavaFX instead of SWT
End of Life

None

Standards

None

Communities

DEMO CAMPS

Once more we visited more 3 demo camps highlighting our new work on smart code editors. A recording of one of the presentations is available at youtube.

FORUMS

No question stays unanswered! We follow this mantra since the beginning and followed it in this release as well.