Jump to: navigation, search

Difference between revisions of "Auto IWG WP1"

(Current Status)
(Content)
(44 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
This is work package 1 of the [[Automotive Industry Working Group]].
 
This is work package 1 of the [[Automotive Industry Working Group]].
  
*Project Lead: Bosch (TBD)
+
* WP Lead: Bosch (TBD)
  
 
== Intent ==
 
== 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 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:
+
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 points out which Eclipse projects and components are actively used in the automotive industry.
Line 19: Line 19:
  
 
The Eclipse Automotive Tool Platform will be made available in the following forms:
 
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 [http://www.eclipse.org/downloads Eclipse.org]
+
* An Eclipse package named '''Eclipse IDE for Automotive Software Developers''' for download at [http://eclipse.org/downloads/index-developer.php Eclipse.org]
* A corresponding [http://wiki.eclipse.org/images/d/d5/Automotive-target.zip 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)
+
* A corresponding target platform definition for download at [http://code.google.com/a/eclipselabs.org/p/eclipse-auto-iwg/downloads/list EclipseLabs.org]
  
 
The Eclipse IDE for Automotive Software Developers is meant to address the following use cases:
 
The Eclipse IDE for Automotive Software Developers is meant to address the following use cases:
Line 33: Line 33:
 
== Content ==
 
== 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 current version of the Eclipse Automotive Tool Platform is based on the [http://wiki.eclipse.org/Juno Juno (Eclipse 4.2)] release stream. It contains the components that are listed in the table below.  
  
The component statuses can have the following values:
+
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
+
* 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
+
* 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
  
  
Line 51: Line 51:
 
! Comment
 
! Comment
 
|-
 
|-
| rowspan="2"| '''Eclipse'''   
+
| rowspan="3"| '''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"| 4.2.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
|
 
|
 +
|-
 +
| Eclipse Product Configuration
 +
| align="center"| 1.0.0
 +
| align="center"| RECOMMENDED
 +
| align="center"| X
 +
| align="center"| X
 +
| Required for building products
 
|-
 
|-
 
| Eclipse Platform Launchers
 
| Eclipse Platform Launchers
| align="center"| 3.5.0
+
| align="center"| 3.6.0
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 66: Line 73:
 
| Required for building products with custom native launchers
 
| Required for building products with custom native launchers
 
|-
 
|-
|rowspan="13"|'''Modeling tools'''
+
| rowspan="13"|'''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.8.1
 
| RECOMMENDED
 
| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 75: Line 82:
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.emf.transaction EMF Model Transaction SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.emf.transaction EMF Model Transaction SDK]
| align="center"| 1.5.0
+
| align="center"| 1.6.0
 
| RECOMMENDED
 
| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 82: Line 89:
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.emf.validation EMF Validation Framework SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.emf.validation EMF Validation Framework SDK]
| align="center"| 1.5.0
+
| align="center"| 1.6.0
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 89: Line 96:
 
|-
 
|-
 
| [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.0
+
| align="center"| 1.3.2
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 96: Line 103:
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.gmp.gmf-notation GMF Notation SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.gmp.gmf-notation GMF Notation SDK]
| align="center"| 1.5.0
+
| align="center"| 1.6.0
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 103: Line 110:
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.gmp.gmf-runtime GMF Runtime SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.gmp.gmf-runtime GMF Runtime SDK]
| align="center"| 1.5.0
+
| align="center"| 1.6.0
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 +
| align="center"| X
 +
| align="center"| X
 +
|
 +
|-
 +
| [http://www.eclipse.org/projects/project.php?id=modeling.gmp.graphiti Graphiti SDK]
 +
| align="center"| 0.9.1
 +
| align="center"| PROPOSED
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
Line 110: Line 124:
 
|-
 
|-
 
| [http://www.eclipse.org/modeling/emft/?project=mwe Modeling Workflow Engine SDK]
 
| [http://www.eclipse.org/modeling/emft/?project=mwe Modeling Workflow Engine SDK]
| align="center"| 1.1.1
+
| align="center"| 1.2.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
|
+
|  
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.m2t.xpand Xpand SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.m2t.xpand Xpand SDK]
| align="center"| 1.0.1
+
| align="center"| 1.2.1
| align="center"| LEGACY
+
| align="center"| DEPRECATED
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
|
+
| New projects should use Xtend.
 
|-
 
|-
| [http://www.eclipse.org/Xtext/#xtend2 Xtend 2 SDK]
+
| [http://www.eclipse.org/projects/project.php?id=modeling.tmf.xtext Xtext SDK]
| align="center"| 2.0.1
+
| align="center"| 2.3.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
|
+
|  
 
|-
 
|-
| [http://www.eclipse.org/projects/project.php?id=modeling.tmf.xtext Xtext SDK]
+
| [http://www.eclipse.org/projects/project.php?id=modeling.mdt.sphinx Sphinx SDK]
| align="center"| 2.0.1
+
| align="center"| 0.7.0
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 +
| align="center"| -
 
| align="center"| X
 
| align="center"| X
| align="center"| X
+
| Not included in Eclipse package because not yet part of simultaneous release train
|
+
 
|-
 
|-
 
| [http://www.eclipse.org/projects/project.php?id=modeling.mdt.uml2 UML2 SDK]
 
| [http://www.eclipse.org/projects/project.php?id=modeling.mdt.uml2 UML2 SDK]
| align="center"| 3.2.0
+
| align="center"| 4.0.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 145: Line 159:
 
|-
 
|-
 
| [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.8.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
|
 
|
|-  
+
|-
| [http://www.eclipse.org/projects/project.php?id=modeling.gmp.graphiti Graphiti SDK]
+
| rowspan="1"|'''Automotive components'''
| align="center"| 0.8.1
+
| [http://www.artop.org Artop SDK]
| align="center"| PROPOSED
+
| align="center"| 3.3.0
 +
| align="center"| RECOMMENDED
 +
| align="center"| -
 
| align="center"| X
 
| align="center"| X
| align="center"| X
+
| Not included in Eclipse package because not an Eclipse project
|
+
 
|-
 
|-
|rowspan="5"|'''Tool components'''
+
| rowspan="4"|'''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"| 2.7.0
+
| align="center"| 8.1.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
| align="center"| X
 
|
 
|
 +
|-
 +
| [http://www.eclipse.org/Xtext/#xtend2 Xtend SDK]
 +
| align="center"| 2.3.1
 +
| align="center"| RECOMMENDED
 +
| align="center"| X
 +
| align="center"| X
 +
|
 
|-
 
|-
 
| [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.0
+
| align="center"| 3.9.0
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 174: Line 196:
 
|-
 
|-
 
| [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.0
+
| align="center"| 3.4.1
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 
| align="center"| X
 
| align="center"| X
Line 180: Line 202:
 
|
 
|
 
|-
 
|-
| [http://www.eclipse.org/mpc Marketplace Client]
+
| rowspan="1"|'''Technology components'''
| align="center"| 1.1.1
+
| [http://www.eclipse.org/projects/project.php?id=technology.nebula Nebula Widgets]
 +
| align="center"| 1.0.0
 
| align="center"| RECOMMENDED
 
| align="center"| RECOMMENDED
 +
| align="center"| -
 
| align="center"| X
 
| align="center"| X
| align="center"| X
+
| Not included in Eclipse package because not yet part of simultaneous release train
|
+
 
|-
 
|-
 
|}
 
|}
Line 191: Line 214:
 
=== Previous versions ===
 
=== Previous versions ===
  
 +
* [[Eclipse Automotive Tool Platform for Indigo (Eclipse 3.7)]]
 
* [[Proposed Content as of March 2009]]
 
* [[Proposed Content as of March 2009]]
  
== Update & Maintenance Strategy ==
+
== Update, Maintenance & Migration Strategy ==
  
 
t.b.d.
 
t.b.d.
Line 208: Line 232:
 
*** Requires service releases beyond SR-1 and SR-2
 
*** Requires service releases beyond SR-1 and SR-2
 
*** Should be addressed in collaboration with [http://eclipse-membership.blogspot.com/2011/05/long-term-support-initiative-workshop.html Long Term Support IWG] and/or [http://www.eclipse.org/org/press-release/20111102_polarsys.php Polarsys IWG]
 
*** Should be addressed in collaboration with [http://eclipse-membership.blogspot.com/2011/05/long-term-support-initiative-workshop.html Long Term Support IWG] and/or [http://www.eclipse.org/org/press-release/20111102_polarsys.php Polarsys IWG]
 +
* 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 ==
 +
 +
* Eclipse IDE for Automotive Software Developers: http://eclipse.org/downloads/index-developer.php
 +
* Target platform definitions for Eclipse IDE for Automotive Software Developers: http://code.google.com/a/eclipselabs.org/p/eclipse-auto-iwg/downloads/list
 +
* Eclipse bugzilla component for Eclipse Automotive IWG: https://bugs.eclipse.org/bugs/buglist.cgi?classification=Eclipse%20Foundation&product=Working%20Groups&component=Automotive
 +
* EclipseLabs project providing Git repos and downloads for Eclipse Automotive IWG: http://code.google.com/a/eclipselabs.org/p/eclipse-auto-iwg
 +
* Eclipse Packaging Project (EPP) bug related to Eclipse IDE for Automotive Software Developers: https://bugs.eclipse.org/bugs/show_bug.cgi?id=369763
  
 
== Open Issues ==
 
== 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)
+
* Settle update, maintenance & migration strategy
* Get Git repository for Eclipse Automotive IWG at http://git.eclipse.org and move implementation-related Eclipse Automotive Tool Platform artifacts right there
+
* Finalize Eclipse package and target platform definition when Eclipse Juno is released
* 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
  
 
[[Category:Auto IWG]]
 
[[Category:Auto IWG]]

Revision as of 06:00, 17 October 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:

  • 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.1 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.1 RECOMMENDED X X
EMF Model Transaction SDK 1.6.0 RECOMMENDED X X
EMF Validation Framework SDK 1.6.0 RECOMMENDED X X
EMF Compare SDK 1.3.2 RECOMMENDED X X
GMF Notation SDK 1.6.0 RECOMMENDED X X
GMF Runtime SDK 1.6.0 RECOMMENDED X X
Graphiti SDK 0.9.1 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.
Xtext SDK 2.3.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 4.0.1 RECOMMENDED X X
XSD - XML Schema Definition SDK 2.8.1 RECOMMENDED X X
Automotive components Artop SDK 3.3.0 RECOMMENDED - X Not included in Eclipse package because not an Eclipse project
Tool components C/C++ Development Tools (CDT) SDK 8.1.1 RECOMMENDED X X
Xtend SDK 2.3.1 RECOMMENDED X X
Graphical Editing Frameworkd (GEF) SDK 3.9.0 RECOMMENDED X X
XML Editors and Tools 3.4.1 RECOMMENDED X X
Technology components Nebula Widgets 1.0.0 RECOMMENDED - X Not included in Eclipse package because not yet part of simultaneous release train

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