This is a pull request based on the latest merge from upstream. It reintroduces all the changes required to comply with the ROS release procedures. With this in place, the whole repository can be checked out into a ROS workspace and be compiled entirely with catkin_make_isolated and also can be released to the ROS (or STRANDS) build farms to have binary packages build. It also adds helper scripts to simply run jarp from command line as jarp.sh (resolving paths to java classes automatically). Package are already build an released via the STRANDS build farm. They can be used by following the instructions at https://github.com/strands-project-releases/strands-releases/wiki and then running sudo-apt-get install ros-indigo-pnp-ros for instance.
So, this PR puts the ROS-ified PNP repository back in line with the main development branch of upstream while keeping all the modification required to make this ROS-friendly.
Also, @cdondrup can have a look as he was planning to use it (potentially).
This is a pull request based on the latest merge from upstream. It reintroduces all the changes required to comply with the ROS release procedures. With this in place, the whole repository can be checked out into a ROS workspace and be compiled entirely with
catkin_make_isolatedand also can be released to the ROS (or STRANDS) build farms to have binary packages build. It also adds helper scripts to simply run jarp from command line asjarp.sh(resolving paths to java classes automatically). Package are already build an released via the STRANDS build farm. They can be used by following the instructions at https://github.com/strands-project-releases/strands-releases/wiki and then runningsudo-apt-get install ros-indigo-pnp-rosfor instance.So, this PR puts the ROS-ified PNP repository back in line with the main development branch of upstream while keeping all the modification required to make this ROS-friendly.
Also, @cdondrup can have a look as he was planning to use it (potentially).