Jump to: navigation, search

Difference between revisions of "Auto IWG WP1"

(Content)
(Content)
Line 41: Line 41:
 
* 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
 
* 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
 
* PROPOSED: The component is proposed to become a new component of the  Eclipse Automotive Tool Platform and already included for evaluation purposes
 
{{message|{{#if:{{{1|}}}|'''{{{1}}}'''<BR>}}'''CAUTION:''' The component versions indicated below are still preliminary. They will be updated to the final versions with the arrival of Indigo SR-2 by Feb 24, 2012.{{#if:{{{2|}}}|{{{2}}}}}|image=Stop.png}}
 
  
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
Line 56: Line 54:
 
| rowspan="2"| '''Eclipse'''   
 
| rowspan="2"| '''Eclipse'''   
 
| [http://www.eclipse.org/projects/project.php?id=eclipse Eclipse SDK]
 
| [http://www.eclipse.org/projects/project.php?id=eclipse Eclipse SDK]
| align="center"| 3.7.1
+
| align="center"| 3.7.2
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 63: Line 61:
 
|-
 
|-
 
| Eclipse Platform Launchers
 
| Eclipse Platform Launchers
| align="center"| 3.5.0
+
| align="center"| 3.5.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 71: Line 69:
 
| rowspan="14"|'''Modeling components'''
 
| rowspan="14"|'''Modeling components'''
 
| [http://www.eclipse.org/projects/project.php?id=modeling.emf Eclipse Modeling Framework (EMF) SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.emf Eclipse Modeling Framework (EMF) SDK]
| align="center"| 2.7.1
+
| align="center"| 2.7.2
 
| RECOMMENDED
 
| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 92: Line 90:
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.emf.compare EMF Compare SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.emf.compare EMF Compare SDK]
| align="center"| 1.2.1
+
| align="center"| 1.2.2
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 113: Line 111:
 
|-  
 
|-  
 
| [http://www.eclipse.org/projects/project.php?id=modeling.gmp.graphiti Graphiti SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.gmp.graphiti Graphiti SDK]
| align="center"| 0.8.1
+
| align="center"| 0.8.2
 
| align="center"| PROPOSED
 
| align="center"| PROPOSED
 
| align="center"| X
 
| align="center"| X
Line 148: Line 146:
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.mdt.sphinx Sphinx SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.mdt.sphinx Sphinx SDK]
| align="center"| 0.8.1
+
| align="center"| 0.7.0
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| -
 
| align="center"| -
Line 162: Line 160:
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.mdt.xsd XSD - XML Schema Definition SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.mdt.xsd XSD - XML Schema Definition SDK]
| align="center"| 2.7.0
+
| align="center"| 2.7.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 170: Line 168:
 
| rowspan="1"|'''Automotive components'''
 
| rowspan="1"|'''Automotive components'''
 
| [http://www.artop.org Artop SDK]
 
| [http://www.artop.org Artop SDK]
| align="center"| 3.2.1
+
| align="center"| 3.2.2
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| -
 
| align="center"| -
Line 178: Line 176:
 
| rowspan="5"|'''Tool components'''
 
| rowspan="5"|'''Tool components'''
 
| [http://www.eclipse.org/projects/project.php?id=tools.cdt C/C++ Development Tools (CDT) SDK]
 
| [http://www.eclipse.org/projects/project.php?id=tools.cdt C/C++ Development Tools (CDT) SDK]
| align="center"| 8.0.0
+
| align="center"| 8.0.2
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 185: Line 183:
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=tools.gef Graphical Editing Frameworkd (GEF) SDK]
 
| [http://www.eclipse.org/projects/project.php?id=tools.gef Graphical Editing Frameworkd (GEF) SDK]
| align="center"| 3.7.1
+
| align="center"| 3.7.2
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 192: Line 190:
 
|-
 
|-
 
| [http://www.eclipse.org/webtools/wst/components/xml/overview.html XML Editors and Tools]
 
| [http://www.eclipse.org/webtools/wst/components/xml/overview.html XML Editors and Tools]
| align="center"| 3.3.1
+
| align="center"| 3.3.2
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X

Revision as of 17:58, 28 April 2012

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:

Stop.png
CAUTION: The component versions in the currently published drafts for Eclipse package and target platform definitions are still preliminary. They will be updated to the final versions with the arrival of Indigo SR-2 by Feb 24, 2012.


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 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
  • 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 3.7.2 RECOMMENDED X X
Eclipse Platform Launchers 3.5.1 RECOMMENDED X X Required for building products with custom native launchers
Modeling components Eclipse Modeling Framework (EMF) SDK 2.7.2 RECOMMENDED X X
EMF Model Transaction SDK 1.5.1 RECOMMENDED X X
EMF Validation Framework SDK 1.5.0 RECOMMENDED X X
EMF Compare SDK 1.2.2 RECOMMENDED X X
GMF Notation SDK 1.5.0 RECOMMENDED X X
GMF Runtime SDK 1.5.0 RECOMMENDED X X
Graphiti SDK 0.8.2 PROPOSED X X
Modeling Workflow Engine SDK 1.1.1 RECOMMENDED X X
Xpand SDK 1.1.1 DEPRECATED X X Use Xtend2 SDK instead
Xtend 2 SDK 2.0.1 RECOMMENDED X X
Xtext SDK 2.0.1 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 3.2.1 RECOMMENDED X X
XSD - XML Schema Definition SDK 2.7.1 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.0.2 RECOMMENDED X X
Graphical Editing Frameworkd (GEF) SDK 3.7.2 RECOMMENDED X X
XML Editors and Tools 3.3.2 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

Open Issues

  • 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
  • Make Sphinx join simultaneous release train
  • Consider adoption of additional components:
    • OSEE
    • ARText