Skip to main content
Jump to: navigation, search

Auto IWG

Revision as of 11:52, 21 July 2011 by (Talk | contribs) (Organization)

This is the starting page for the Automotive Industry Working Group at Eclipse.


  • To provide an infrastructure for tool development required by the automotive industry
  • To address and support the needs for the whole automotive software development cycle
  • To avoid that the same non-competitive basic tool functionality is redeveloped over and over again
  • To join forces and meet current and future requirements in terms of tool runtime performance and memory consumption


Spokesperson: Andreas Graf, itemis AG

Steering Committee Chair: Ignacio Garro, Continental AG

Steering Committee: Awaiting management approval - see [1]

For more information, contact ralph (dot) mueller (at) eclipse (dot) org

Meetings and Activities

Tech Meeting Suttgart 08. June 2011

Was held at the Itemis AG office in Stuttgart / Vaihingen. The minutes of the meeting were prepared by Ralph Mueller, Eclipse foundation. They are available in the mailing list [2]

Proposal for Creation of Auto IWG published

You can find the proposal here [3]

Tech Meeting Kornwestheim 21. October 2010

Was held at the KuglerMaag Cie. facilities in Kornwestheim. The minutes fo the meeting were prepared by Andreas Graf, Itemis AG. They are available in the mailing list [4].

Tech Meeting Kornwestheim 19. July 2010

Was held at the KuglerMaag Cie. facilities in Kornwestheim. The minutes fo the meeting were prepared by Andreas Graf, Itemis AG. They are available in the mailing list [5].

Eclipse distribution for Automotive Tool Developers

A dedicated Eclipse distribution for Automotive Tool Developers could be a first concrete step and deliverable of this IWG. The idea is to identify a set of existing Eclipse projects and components that are typically required and used in automotive tool development and make them available as a new Eclipse distribution at Though not including any automotive specific content yet, we believe that such an Eclipse distribution makes anyway sense because of 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 release which automotive tool development is typically based on
  • It eases the provision and maintenance of the Eclipse platform required for automotive tool development

It is important to note that such an Eclipse distribution is addressed to automotive tool developers but not to automotive tool users. In other words, it is not meant as something that ECU software developers could use out of the box and find useful. It is intended as starting point and target platform which ECU software tool developers can base their work on. What ECU software developers will eventually be provided with, are mostly the tools resulting for the ECU software tool development plus the dependent parts of the Eclipse Tool Developer distribution.

Based on the current state of discussion the following Eclipse projects and components have been deemed relevant to an Eclipse distribution for Automotive Tool Developers:

From Artop (see [6]):

* Eclipse SDK 3.4.2 (Ganymede)
* EMF Query SDK 1.2.0
* EMF Transaction SDK 1.2.3
* EMF Validation SDK 1.2.1
* GEF SDK 3.4.2
* GMF SDK 2.1.3
* MDT OCL SDK 1.2.3
* MDT UML2 SDK 2.2.2
* Orbit R20080807152315
  - org.apache.commons.lang 2.3.0
  - org.jdom 1.0.0

Additional projects and components from EDONA (see [7]):

* Acceleo 2.4.0 SDK
* Antlr 4.1.1
* M2M ATL SDK 2.0.2
* M2T MTL SDK 0.7.0RC1
* Papyrus 1.11.0
  - Papyrus EADL
  - Papyrus SYSML 1.1.5
* HMI svg format
* East-adl 2 experimentation

Additional projects and components requested by IWG members:

* oAW (open Architecture Ware)
* CDT 4.0
* CDT 5.0
* WST (XML Editor 3.0)
* Nebula Widgets
* company specific plugins
* Mylyn
* M2M (QVT Operational)
* CLI, Log4J
* P2 (Update / Install Manager)
* Device Debugging Memory View 0.9
* Update Manager


In addition to the list of frequently used components, the working group also identified a list of topics that should be adressed in future distributions:

  • Broad support of MISRA-C in the components
  • Target Device emulation / Simulation
  • Strategy for a model repository / distributed collaboration aspects
  • Support for Component testing and Code Coverage Analysis
  • Full Debugger Support
  • Build management support
  • C preprosessor enhancement
  • Product line support / Variant management.
  • C metamodel that includes preprocessor statements.
  • C++ (ANSI-C++ and/or embedded specific dialects like Extended Embedded C++ )


Auto IWG Mailing List
AUTOSAR Tool Platform (Artop)
Edona Project
Topcased Project
Sphinx Proposal

Back to the top