Skip to content
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

Divergence of MotionPlanRequest.msg between ROS 1 and 2 Versions #156

Open
acbuynak opened this issue Apr 1, 2023 · 0 comments
Open

Divergence of MotionPlanRequest.msg between ROS 1 and 2 Versions #156

acbuynak opened this issue Apr 1, 2023 · 0 comments

Comments

@acbuynak
Copy link

acbuynak commented Apr 1, 2023

Stumbled across a breaking change between versions of msg/MotionPlanRequest.msg while building a ROS Bridge. Reading through Issues/PR's it looks like there's an intentional history. Adding this issue to highlight the difference.

Brief History:

#113, message field was added, but wrong name used.
#122, attempts to correct field names.
#130, rewrite of 122, successfully merged into master.

All ROS 2 versions appear to be 9 commits behind, critically f562cc8

I'm unfamiliar with the ROS 2 moveit ecosystem to say the appropriateness of whether it's okay for these to match. At this time, users attempting to bridge MoveIt messages are unable to do so without modifying one side or the other. Given ROS Noetic is around until 2025, it may be useful to have them match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant