Repository Summary
| Checkout URI | https://github.com/rosjava/rosjava_messages.git |
| VCS Type | git |
| VCS Version | indigo |
| Last Updated | 2016-12-12 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
| Name | Version |
|---|---|
| rosjava_messages | 0.2.3 |
README
RosJava Messages
History
Some history for the annals of time and also for future devs who are wondering about the boundaries defining the choice of message packages that form the conglomeration that is rosjava messages.
Several approaches were tried/tested, discarded until we have what is here.
Scan rosdistro to discover all possible message packages
Experimental packages often appear/disappear and this triggered too much manual intervention to maintain. There is also far too many packages that have code with it too. This is awkward for rosjava to depend on - I prefer message only packages and have encouraged upstream folk to shift their messages to message only packages in certain instances.
Used for hydro, but dropped for indigo
Minimal set of messages directly used by rosjava/android
Easiest to maintain, but not so useful for users - they have to then go off and generate many message packages themselves, even if only using some of the more common packages.
Used for indigo, but dropped shortly afterwards
Minimal set and finite set of stable, popular packages
Relatively easy to maintain and important for maven repo users since they will not want to go and directly build message packages themselves. If I get a request, I usually add to the list to support these users.
Used in indigo
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/rosjava/rosjava_messages.git |
| VCS Type | git |
| VCS Version | hydro |
| Last Updated | 2015-05-29 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
| Name | Version |
|---|---|
| rosjava_messages | 0.1.345 |
README
RosJava Messages
Message Artifact Generation
Your regular rosjava message project does not need this complexity!
The gradle magic in settings.gradle is responsible for kickstarting the following very useful things for a big release of message packages:
- Generating an artifact for every listed (in the package.xml) ros message package.
- Discovering & applying the underlying package version and dependency information to the artifact.
It manages the correspondence by dynamically spawning subprojects from a template build.gradle. This saves a very large amount of tedious and repetitive gradle management.
The package version and dependency information is extracted by the catkin gradle plugin that can be found in rosjava_bootstrap.
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/rosjava/rosjava_messages.git |
| VCS Type | git |
| VCS Version | kinetic |
| Last Updated | 2016-12-24 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
| Name | Version |
|---|---|
| rosjava_messages | 0.3.0 |
README
RosJava Messages
History
Some history for the annals of time and also for future devs who are wondering about the boundaries defining the choice of message packages that form the conglomeration that is rosjava messages.
Several approaches were tried/tested, discarded until we have what is here.
Scan rosdistro to discover all possible message packages
Experimental packages often appear/disappear and this triggered too much manual intervention to maintain. There is also far too many packages that have code with it too. This is awkward for rosjava to depend on - I prefer message only packages and have encouraged upstream folk to shift their messages to message only packages in certain instances.
Used for hydro, but dropped for indigo
Minimal set of messages directly used by rosjava/android
Easiest to maintain, but not so useful for users - they have to then go off and generate many message packages themselves, even if only using some of the more common packages.
Used for indigo, but dropped shortly afterwards
Minimal set and finite set of stable, popular packages
Relatively easy to maintain and important for maven repo users since they will not want to go and directly build message packages themselves. If I get a request, I usually add to the list to support these users.
Used in indigo