Sorry for crossposting, but I thought you folks might be interested in this.
Hey,
I just made public a set of Java and Android bindings for ROS2, I wrote
them a while ago, but they needed some updates and never had made a
proper release of them before.
Anyway, I’ve pushed it all to GitHub, they are licensed as Apache 2.0. You can follow the instructions
on [1] if you’d like to try out the examples.
There’s a few caveats (it wouldn’t be a ROS project if the word “caveat” weren’t in the announcement):
Not all of the API is implemented, things like QoS profiles are missing for example.
Domains are not supported, I stil lhave pending implementing a mechanism for setting the domain id programmatically.
No support for services or intraprocess communication.
Lack of documentation and tests
In the following days I’ll polish a few things and also put up a demo, but meanwhile you can use all this to write ROS2 applications that can run on an Android device, on a PC with the JRE and communicate with other applications written in Python or C++.
How to add & run tests (JUnit or with other testing framework) ?
rcljava applications can use Gradle as a build system, so adding tests is
similar to any other Gradle project. However, rcljava would benefit a lot
from a specialized Gradle plug-in, so Gradle files for rcljava applications
could be much more streamlined.
As for rcljava itself, tests need to be integrated with CMake though,
because rcljava itself does not use Gradle.
Do you plan to add service support ?
Yes! However that requires some thought as to how to integrate services
directly with rcl instead of replicating the code from rclcpp.
Do you plan to add launch support ?
Not sure I understand what you mean. That part of the infrastructure
belongs in ROS2 itself, not in the language-specific bindings. Could you
expand this a bit?
Do you plan to add parameter/dynamic-reconfiguration support ?
Much like services, support for parameters need to exist first in rcl, and
then implemented in the client libraries. Services are already available in
rcl, but unfortunately parameters aren’t yet.
Dynamic reconfiguration is not implemented in ROS2 yet.
I propose my help.
Great! What would you like to work on? My first thought would be refining
what’s already in rcljava (build system, tests, etc.), before implementing
any new features (e.g. services), but if there’s anything else you’d like
to work on, just let me know.
Header file (but i see you push-it in your last commit why not use OSRF ?)
QoS profile
Testing (but I need to add on gradle)
Java Service (need to add on JNI call)
Java Parameter (need rcl finished by core team)
I propose to you to make a clean Merge Request of JavaDoc and Testing.
For the launch case :
Nothing was define in ROS2 design page, but by experience of ROS1 if i make a xxxxxx.laucnh file and java is special.
In your implentation you need to :
eg. java -cp install_isolated/rosidl_generator_java/share/rosidl_generator_java/java/rosidl_generator_java.jar: ....
I would like to know if is possible to generate a simple script for shortcut the launch.
eg. talker_java.sh (or without exention)
Sorry for the slow response, been travelling lately.
This is impressive, thank you so much!
ros2_java is an independent project, as such, the copyright ownership is not under OSRF’s name. This is fairly common with other packages, like rosjava, whose copyright is owned by Google.
I’ll reply with more detail in the pull requests you have submitted on GitHub.
I think that’d be a bit complicated, because the JAR files may be installed anywhere and the script couldn’t know that. But if you find a way to generate such script, I’d love to add it to ros2_java
