Building on work related to issue #709

======================================================================
FAIL: test_get_msg_text (test_rosmsg.TestRosmsg)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/gerkey/code/rosmsg-tests/src/ros_comm/tools/rosmsg/test/test_rosmsg.py", line 74, in test_get_msg_text
    self.assertEquals(text, rosmsg.get_msg_text(type_, raw=True))
AssertionError: 'test_rosmaster/Empty empty\n' != 'Empty empty\n'

From what I can see, rosmsg.get_msg_text() used to have a 'fulltext' option which would refer to the msg types with their package name included ('test_rosmaster/Empty empty\n' vs 'Empty empty\n', as in the error output). This was removed in ef2beb7, but now having the parameter raw=False returns msgs in fulltext, while raw=True doesn't.

The tests are failing because they don't expect this discrepancy.

The current behaviour is:
With raw=False, messages are: recursive, whitespace removed, fulltext.
with raw=True, messages are not recursive, with whitespace not removed, and not fulltext.

I updated the tests to match the current behaviour of get_msg_text/get_srv_text, but it's possible that the appropriate fix is actually the other way around, as, judging from this comment in the previously failing test, the behaviour when raw=False vs True used to be different (with respect to fulltext).