Jump to: navigation, search

Auto IWG WP1

Eclipse Automotive Tool Platform

This is work package 1 of the Automotive Industry Working Group.

  • WP Lead: Bosch (TBD)

Intent

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 much 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

Concept

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 for download at EclipseLabs.org

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

Content

The current version of the Eclipse Automotive Tool Platform is based on the Juno (Eclipse 4.2) release stream. It contains the components that are listed in the table below.

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
  • DEPRECATED: 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 Eclipse SDK 4.2.0 RECOMMENDED X X
Eclipse Product Configuration 1.0.0 RECOMMENDED X X Required for building products
Eclipse Platform Launchers 3.6.0 RECOMMENDED X X Required for building products with custom native launchers
Modeling components Eclipse Modeling Framework (EMF) SDK 2.8.0 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.3.0 RECOMMENDED X X
GMF Notation SDK 1.5.0 RECOMMENDED X X
GMF Runtime SDK 1.5.0 RECOMMENDED X X
Graphiti SDK 0.9.0 PROPOSED X X
Modeling Workflow Engine SDK 1.2.1 RECOMMENDED X X
Xpand SDK 1.2.1 DEPRECATED X X New projects should use Xtend.
Xtend SDK 2.3.0 RECOMMENDED X X
Xtext SDK 2.3.0 RECOMMENDED X X
Sphinx SDK 0.7.0 RECOMMENDED - X Not included in Eclipse package because not yet part of simultaneous release train
UML2 SDK 4.0.0 RECOMMENDED X X
XSD - XML Schema Definition SDK 2.8.0 RECOMMENDED X X
Automotive components Artop SDK 3.2.2 RECOMMENDED - X Not included in Eclipse package because not an Eclipse project
Tool components C/C++ Development Tools (CDT) SDK 8.1.0 RECOMMENDED X X
Graphical Editing Frameworkd (GEF) SDK 3.8.0 RECOMMENDED X X
XML Editors and Tools 3.4.0 RECOMMENDED X X

Previous versions

Update, Maintenance & Migration Strategy

t.b.d.

Some ideas:

  • 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
  • Migration strategy:
    • Keep deprecated components available as long as necessary, i.e., known usages exist
    • Identify migration activities required for getting rid of dependencies to deprecated components
    • Remove deprecated components in newer versions of the platform when no longer needed

Resources

Open Issues

  • Settle update, maintenance & migration strategy
  • Finalize Eclipse package and target platform definition when Eclipse Juno is released
  • Make Sphinx join simultaneous release train
  • Consider adoption of additional components:
    • OSEE
    • ARText