Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Auto IWG"
Line 8: | Line 8: | ||
* To join forces and meet current and future requirements in terms of tool runtime performance and memory consumption | * To join forces and meet current and future requirements in terms of tool runtime performance and memory consumption | ||
− | == Activites | + | == Activites == |
+ | |||
+ | The following topics are currently under discussion: | ||
+ | |||
+ | * Defintion of collaboration mode and structure of this IWG | ||
+ | * Provision of an Eclipse distribution for Automotive Tool Developers | ||
+ | |||
+ | == 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 in automotive tool development and make them available as a new Eclipse distribution at Eclipse.org. 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 automotive industry | ||
+ | * It gives an orientation regarding the Eclipse release automotive tool development is typically based on | ||
+ | * It eases the acquistion and maintenance of Eclipse platform automotive tool development | ||
+ | |||
+ | Based on the current state of discussion the following Eclipse projects and components have been deemed relevant to such a distribution: |
Revision as of 19:07, 11 March 2009
This is the starting page for the Automotive Industry Working Group at Eclipse.
Objectives
- 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
Activites
The following topics are currently under discussion:
- Defintion of collaboration mode and structure of this IWG
- Provision of an Eclipse distribution for Automotive Tool Developers
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 in automotive tool development and make them available as a new Eclipse distribution at Eclipse.org. 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 automotive industry
- It gives an orientation regarding the Eclipse release automotive tool development is typically based on
- It eases the acquistion and maintenance of Eclipse platform automotive tool development
Based on the current state of discussion the following Eclipse projects and components have been deemed relevant to such a distribution: