Eclipse SDV Hephaestus centralizes and standardizes build, tooling, and development environments across Eclipse SDV projects to reduce duplication, enable seamless integration and open-source development workflows.
In Scope
- Bazel-based build and dependency management as the harmonized build system, enabling joint integration of multiple Eclipse SDV components
- Other build and dependency management systems e.g. Cargo should be supported
- Doc-as-Code via Sphinx-Needs, establishing a digital thread linking requirements to technical specifications and test execution results
- Using the Eclipse Common Build Infrastructure
- Pilot adoption with Eclipse S-CORE, Eclipse OpenSOVD, and Eclipse Automotive API Framework
- SIL KIT (Eclipse OpenXilEnv) as a candidate for tool integration.
- Qualification process compliant with ASPICE and ISO 26262, preparation and tooling support only
- Automotive Edge but exploring potential synergies between edge and cloud
Out of Scope
- Actual Safety Certification (such as receiving a final product certificate) and the management of associated liability are excluded, because this is considered as a part of a business model or private agreement between contractual partners
- Mandatory integration of commercial or closed-source tools. These remain optional via well-defined plugin interfaces
- Replacing project-specific domain logic
