rosjava/rosjava_core — pull request #172 by stonier (2013-09-04 03:26:03+00:00)
Title: Fixed horizon message generation (no more ROS_PACKAGE_PATH scope).

**Problems**

* Difficult to define and release a fixed entity that is the rosjava_core
* If you have your own custom messages, you need to install sources anyway, not the release
** And then recompile everything from the bottom (rosjava_core/rosjava_messages).
** The other option is to get rosjava_core released with your msg package, but that can't avoid being a circuitous path to get a simple job done.
* Ensuring you have all the correct msg packages installed is a mysterious process that requires a human.

**The Technical Issue**

* rosjava_messages is a variable beast dependant on the current ROS_PACKAGE_PATH

**Proposed Solution**

Avoid relying on ROS_PACKAGE_PATH and setup a coded, fixed dependency boundaries. No source code change needed, just gradle scripting.

**Results**

* Can generate msg packages outside rosjava_core.
* The rosjava_core release package is fixed, doesn't need obtuse workarounds like in https://github.com/rosjava/rosjava_mvn_repo/issues/3
* The package.xml's can now properly sequence builds across multiple stacks without requiring a magical rebuild of the core.