Skip to content

Move launch packages into autoware_launch #5912

Closed
@xmfcx

Description

@xmfcx

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I've agreed with the maintainers that I can plan this task.

Description

Parent Discussion: Merge launch/configuration repositories under autoware_launch repository #5839

This issue proposes merging several configuration-related repositories into the autowarefoundation/autoware_launch repository. The goal is to simplify the configuration and integration process of Autoware by consolidating related packages under a single repository while maintaining them as separate ROS 2 packages.

Purpose

The current configuration system in Autoware is fragmented across multiple repositories, making it cumbersome for users to manage, version, and customize for their own vehicle setups. This consolidation aims to:

  • Reduce complexity for end users and integrators
  • Improve maintainability and traceability of configuration changes
  • Set the foundation for future improvements to the launch system

Possible approaches

Definition of done

Note: autoware_individual_params will be handled in a separate issue. We will remove the dependency to autoware_individual_params rather than merging it to autoware_launch

Metadata

Metadata

Assignees

Labels

component:launchLaunch files, scripts and initialization tools. (auto-assigned)

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions