Overview

This makes use of maven packaging and repositories to pull in rosjava and the message dependencies you need for your project. What this means is that rosjava development is now decoupled from catkin/ros and you may use whatever development environment you wish so long as it has support for pulling artifacts from maven repositories.

The Rosjava Maven Repository

• The RosJava Maven Repository

This includes artifacts from every release (hydro/indigo/kinetic..). You might have to do about of investigative work to work out which versions apply to kinetic artifacts. Typically core ROS stacks for kinetic are between 0.3 and 0.4. Message artifacts are simply the same version as those built for debs on kinetic.

Development Environments

We don't use this workflow ourselves for rosjava yet (we do for android). If you decide to work in this manner, please update the wiki with some notes on how you did so. If you have questions on how it might work in your scenario, ask us on the sig mailing list.

Gradle

To utilise the repository, simply include it in the list of repositories you would normally pass to the gradle maven repository dependency closure in build.gradle. An example:

repositories {
  maven {
    url "https://github.com/rosjava/rosjava_mvn_repo/raw/master"
  }
  mavenLocal()
  jcenter()
}

and structure your subproject dependencies like:

dependencies {
  compile 'org.ros.rosjava_core:rosjava:[0.3,0.4)'
  compile 'org.ros.rosjava_messages:geometry_msgs:[1.12,1.13)'

More detailed help on how gradle handles this can be found in the official gradle Dependency Management Basics and Depedency Management tutorials.

Eclipse

Gradle