xacro warnings

[osrf-migration]

Original report (archived issue) by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

---

When launching VMRC with:

roslaunch robotx_gazebo sandisland.launch

there are two xacro warnings:

Warning [parser.cc:644] XML Attribute[xmlns:xacro] in element[sdf] not defined in SDF, ignoring.
Warning [parser.cc:644] XML Attribute[xmlns:xacro] in element[world] not defined in SDF, ignoring.

[osrf-migration]

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

---

• set assignee_account_id to "5b04a6cf8a69f52b3ba2e5db"
• set assignee to "kev-the-dev (Bitbucket: kev-the-dev)"

[osrf-migration]

Original comment by Kevin Allen (Bitbucket: kev-the-dev).

---

This may be unavoidable, as this tag is needed to generate xacro files. However, I think it is a good idea to disable running gazebo with --verbose by default, as it mostly just spams the user. This will prevent the warning from being printed

[osrf-migration]

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

---

Thanks, that could be a workaround if we can't avoid the warning.

[osrf-migration]

Original comment by Brian Bingham (Bitbucket: brian_bingham).

---

I believe I see this warning even with verbose=false in the launch file. The warning is a bit confusing since it suggests that some unknown parts of the world/models are being ignored.

[osrf-migration]

Original comment by Brian Bingham (Bitbucket: brian_bingham).

---

In addition I get this xacro warning...

Warning [parser.cc:437] Converting a deprecated SDF source[data-string].

[osrf-migration]

Original comment by Kevin Allen (Bitbucket: kev-the-dev).

---

I don't see that new one, but you are correct the other two appear will still appear with verbose off because they are warnings. Unfortunately, we can't use xacro without that tag, and SDF will warn about anything it doesn't recognize (even though it causes no issue).

[osrf-migration]

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

---

• set milestone to "0.2"

[osrf-migration]

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

---

• changed state from "new" to "resolved"

I'm closing this issue, as right now I believe the only two warnings that we see are expected and unavoidable. Feel free to reopen if new warnings appear.