-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
planning/control component is dependent on the packages outside of planning/control component #8805
Comments
@youtalk |
@takayuki5168 I only checked by CI builds.
|
If we are going to include tier4_control_launch and tier4_planning_launch, I had to add the following dependencies as well:
|
This pull request has been automatically marked as stale because it has not had recent activity. |
@takayuki5168 Great work! Thank you for sharing. To also remove |
Checklist
Description
autowarefoundation/autoware#5194 found that the planning/control component is dependent on the following packages outside of the planning/control component.
Since the dependencies will no longer follow a parent-child relationship, the components become tightly coupled.
Purpose
Ensure that there are no dependency packages spanning across components. Connections between components should depend only on the
core
packages or theautoware.universe/common
packages.Possible approaches
Ensure that there are no dependency packages spanning across components. Connections between components should depend only on the
core
packages or theautoware.universe/common
packages.Definition of done
The planning/control packages will no longer directly depend on the following packages.
The text was updated successfully, but these errors were encountered: