Auto IWG WP1
Eclipse Automotive Tool Platform
This is work package 1 of the Automotive Industry Working Group.
- Project Lead: Bosch (TBD)
One key activity of the Eclipse Automotive IWG is to define and provide an Eclipse Automotive Tool Platform consisting of selected existing Eclipse components that are typically required and used in the automotive industry. The intention of this platform is to provide a reference for both vendors and users of Eclipse-based automotive software design tools. It does not necessarily include any content that is really specific to automotive (at least not at the beginning), but will still be a great deal of help for the following reasons:
- It points out which Eclipse projects and components are actively used in the automotive industry.
- It gives an orientation regarding the Eclipse releases and component versions which Eclipse-based automotive software design tools are or should be based on.
- It provides a reference enabling Eclipse-based automotive software design tools to be provided as pluggable components (update sites), as opposed to being shipped only in the form of complete products including the tool itself and the whole Eclipse platform.
- It provides the basis for reliably and consistently integrating Eclipse-based automotive software design tools from different vendors and/or complementary in-house tools to user-defined design tool chains.
- It is complemented by a cross-organizational strategy defining
- when and how often the Eclipse Automotive Tool Platform should updated to newer versions of Eclipse
- for how long older versions of the Eclipse Automotive Tool Platform should be actively supported
The Eclipse Automotive Tool Platform will be made available in the following forms:
- An Eclipse package named Eclipse IDE for Automotive Software Developers for download at Eclipse.org
- A corresponding target platform definition attached to this wiki page (might later be moved to a still be to created Git repository for the Eclipse Automotive IWG)
The Eclipse IDE for Automotive Software Developers is meant to address the following use cases:
- As is usage for working on embedded automotive control software
- Base platform for composing user-defined automotive software design tool chains out of vendor-provided tools and complementary in-house tools
- Reference platform for testing automotive software design tools being shipped as pluggable components (update sites)
The target platform definition is provided to support the following use cases:
- As is usage as target platform for the development of automotive software design tools
- Starting point for defining target platforms for the development of automotive software design tools that include all Eclipse Automotive Tool Platform components and complementary components from the Eclipse ecosystem
The following table lists the components that are part of the Eclipse Automotive Tool Platform. Each component is described by its name, version, status, and an optional comment. For the sake of a better overview, the components are grouped in categories.
The component statuses can have the following values:
- RECOMMENDED : The component is included in the Eclipse Automotive Tool Platform and recommended to be used for the development of in automotive software design tools or applications
- LEGACY : The component is still included in the Eclipse Automotive Tool Platform to ensure backward compatibility but no longer recommended to be used in new automotive software design tools or applications
- PROPOSED : The component is proposed to become a new component of the Eclipse Automotive Tool Platform and already included for evaluation purposes
|Category||Name||Version||Status||Included in Eclipse package||Included in target platform||Comment|
|Eclipse Platform Launchers||3.5.0||RECOMMENDED||X||X||Required for building products with custom native launchers|
|Modeling tools||Eclipse Modeling Framework (EMF) SDK||2.7.1||RECOMMENDED||X||X|
|EMF Model Transaction SDK||1.5.0||RECOMMENDED||X||X|
|EMF Validation Framework SDK||1.5.0||RECOMMENDED||X||X|
|EMF Compare SDK||1.2.0||RECOMMENDED||X||X|
|GMF Notation SDK||1.5.0||RECOMMENDED||X||X|
|GMF Runtime SDK||1.5.0||RECOMMENDED||X||X|
|Modeling Workflow Engine SDK||1.1.1||RECOMMENDED||X||X|
|Xtend 2 SDK||2.0.1||RECOMMENDED||X||X|
|XSD - XML Schema Definition SDK||2.7.0||RECOMMENDED||X||X|
|Tool components||C/C++ Development Tools (CDT) SDK||2.7.0||RECOMMENDED||X||X|
|Graphical Editing Frameworkd (GEF) SDK||3.7.0||RECOMMENDED||X||X|
|XML Editors and Tools||3.3.0||RECOMMENDED||X||X|
Update & Maintenance Strategy
* Update strategy: e.g., ** Upon every Eclipse release and Eclipse service release (e.g. Juno, Juno SR-1, Juno SR-2) ** Upon every 2nd Eclipse release and every Eclipse service release (e.g. Juno, Juno SR-1, Juno SR-2, but not Kepler, Kepler SR-1, Kepler SR-2) ** According to dedicated update roadmap ** Active support of the two latest Eclipse versions (as done in Artop) * Maintenance strategy: ** Keep old versions available in same way as done for other Eclipse packages ** Enable bugfixes/small enhancements on old versions *** Requires service releases beyond SR-1 and SR-2 *** Should be addressed in collaboration with Long Term Support IWG and/or Polarsys IWG
- Get first version of Eclipse IDE for Automotive Software Developers out of the door (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=369763 for details)
- Get Git repository for Eclipse Automotive IWG at http://git.eclipse.org and move implementation-related Eclipse Automotive Tool Platform artifacts right there
- Get Bugzilla space at http://bugs.eclipse.org to track and discuss change requests, update and maintenance activities