-
Notifications
You must be signed in to change notification settings - Fork 114
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
#19 introduced a conflicting set of launch files #20
Comments
This sounds very much like we should fix it, I agree.
It might not confuse beginners who copy the tutorial, but
slightly more experienced users who use roslaunch "properly"..
One way (would break the setup assistant though) would be to
prefix all the launch files. How about renaming the folders to
`moveit_fanuc_moveit_config`, etc., and make them proper packages (again)?
|
Making them separate packages will probably break a lot of tests (which rely on moveit_resources being the package that provides all those launch files). |
Seems like the simplest fix for now is to prefix the roslaunch files as @v4hn suggested. Rename them to fanuc_demo.launch and panda_demo.launch |
Fixed for quite some while. |
With #19 being merged, we now have the following error:
I think, as long as the tests explicitly specify which launch file(s) to use, there is no problem.
Nevertheless, should we take any action, e.g. remove fanuc, or add prefixes to all launch files?
The text was updated successfully, but these errors were encountered: