Eclipse Sphinx 0.8.0

Release Date
Deliverables

This release will be delivered via a p2 repository including SDK (runtime, sources and documentation), non-SDK (runtime only), examples and test utilities.

Compatibility

Sphinx aims to provide binary compatible APIs.

Internationalization

The Sphinx plug-ins are prepared for internalization using the usual Eclipse plugin.properties mechanism. Default language is English. Currently no other translations exist.

Target Environments

The Sphinx 0.8 targets a defined set of other Eclipse components (e.g. platform, EMF, etc.) originating from the following release trains: Kepler (Eclipse 4.3) & Luna (Eclipse 4.4). 

Sphinx builds and testing will always be based on latest available milestone build or service release of Eclipse (e.g. Eclipse 4.4M3, 4.4.1). Sphinx will work with Java 5 or higher.

Name Date Description
M3 2013/11/20
M4 2013/12/25
M5 2014/02/05
M6 2014/03/19
M7 2014/05/14
RC1 2014/05/28
RC2 2014/06/04
RC3 2014/06/11
RC4 2014/06/18
0.8.0 Final 2014/06/25
Themes

Reusability, Interoperability and Performance

Even though initially driven by the automotive industry, Sphinx is a generic platform for creating model-driven tool environments and can be reused in others domains like aerospace, finance, etc. It facilitates the interoperability of modeling tools based on different metamodels or Domain-Specific Languages (DSLs). Sphinx already includes many optimizations to improve the runtime performance when it comes to handling and processing bigger models (e.g., file content type detection, model loading or unloading). Nevertheless, further and potentially quite significant performance improvements could be achieved by introducing a model indexing service in Sphinx and using index-backed queries to perform runtime-intensive operations on EMF models (e.g., proxy resolution, model validation, deletion of model elements).
This release is part of Luna