Moved ROSARIA package to seperate directory.
Publishing pose information in meters (as oposed to Aria - in milimeters).
Fixed the node to do a gracefull shutdown.

Node is deleted before the program exits, and the destructor
disconnects from robot and shuts down Aria. (No more beeping
from the robot's watchdog after killing the node.)
Added frame_id in order to enable visualization in rviz.
Aria (ArRobot::getVel()) also returns velocity in mm/s.

Odometry message should be completely fixed now.
Documenting repository - babystep.
Fixed high CPU usage by using ros::spin().
Replaced 'while(n.ok()) {ros::spinOnce(); }' with ros::spin().
Documentation: manifests edited.
Added bumper compatibility (message and topic publishing)
ROSARIA: Doesn't assume known number of bumpers when using ROS_INFO.
The ROSARIA node now supports the use of tf_prefixes.
See http://www.ros.org/wiki/geometry/CoordinateFrameConventions#tf_prefix for details.
Added basic support for sonars.
In order to use them, set the private use_sonar parameter to True, and publish a transform (e.g. using the static_transform_publisher) from the centre of the sonar ring to the base_link (or other base frame) of the robot. This means that you basically only need to account for the z-offset of the sonars from the base_link.

This code has not been tested on robots with multiple sonar rings at different heights (such as the Peoplebot) and is likely to require some modifications: The ARIA library does not appear to return z coordinates of sonar readings (or sonar senors), which means that other means would be necessary to distinguish between the upper and lower sonar ring of a Peoplebot. Additionally, the difference in x,y,z of the sonar rings would need to be applied to the sonar readings of the upper ring so that the published point cloud is correct.
Enhanced sonar support from Michiel.

Droped the use_sonar private param. Sonar topic is allways advertized,
but the readings are taken (and published) only if there are subscribers.
Updated ROSARIA for fuerte.

Thanks to David Portugal for pointing out problems with Odometry messages
in fuerte.
Support for remote robots through a TCP/IP connection.

This is a revised patch from Jesús Miguel Torres Jorge which closes
issue 3.
Added odom to base_link transform.
Right after running catkinize.
Edited the results of catkinization.

Stumbled on the following issues:
- unicode in package.xml unsupported
https://github.com/ros-infrastructure/catkin_pkg/commit/eca2dee05e26fc750a5a58f490e97548e25c7bb2

- rosdep-source removed!!!
https://github.com/ros/rosdep/issues/210
https://github.com/ros/rosdep/commit/fc8b56be072ab672344c747de815daaacf2e9834#commitcomment-2370278

- depends from .rdmanifest ignored

ROSARIA now compiles, but the libaria dependency handled by hand.
Adding libaria.rdmanifest.
ROSARIA license corrected (GPLv2)

Since ARIA library is GPLv2, so are the derived products, e.g. software that links
to the library.

Removed Aria package (external library wrapper), since that's not the recommended
way of dealing with external libraries for catkinized packages. We'll handle ARIA
using rosdep.