Revision history [back]

I just saw the wiki documentation for that is using the ivy style for open ranged dependencies. If you're using the maven repo directly, you need the maven style format (refer to this issue thread). That is,

dependencies {
    compile 'org.ros.android_core:android_gingerbread_mr1:0.1.+'
    compile 'org.ros.android_core:android_honeycomb_mr2:0.1.+'
    compile 'org.ros.rosjava_core:rosjava:0.1.+'
}

should be

dependencies {
    compile 'org.ros.android_core:android_gingerbread_mr1:[0.1,0.2)'
    compile 'org.ros.android_core:android_honeycomb_mr2:[0.1,0.2)'
    compile 'org.ros.rosjava_core:rosjava:[0.1,0.2)'
}

I updated the wiki to reflect this. Try that and let me know how it goes.

I just saw the wiki documentation for that is using the ivy style for open ranged dependencies. If you're using the maven repo directly, you need the maven style format (refer to this issue thread). That is,

dependencies {
    compile 'org.ros.android_core:android_gingerbread_mr1:0.1.+'
    compile 'org.ros.android_core:android_honeycomb_mr2:0.1.+'
    compile 'org.ros.rosjava_core:rosjava:0.1.+'
}

should be

dependencies {
    compile 'org.ros.android_core:android_gingerbread_mr1:[0.1,0.2)'
    compile 'org.ros.android_core:android_honeycomb_mr2:[0.1,0.2)'
    compile 'org.ros.rosjava_core:rosjava:[0.1,0.2)'
}

I updated the wiki to reflect this. Try that and let me know how it goes.

I just saw the wiki documentation for that is using the ivy style for open ranged dependencies. If you're using the maven repo directly, you need the maven style format (refer to this issue thread). That is,

dependencies {
    compile 'org.ros.android_core:android_gingerbread_mr1:0.1.+'
    compile 'org.ros.android_core:android_honeycomb_mr2:0.1.+'
    compile 'org.ros.rosjava_core:rosjava:0.1.+'
}

should be

dependencies {
    compile 'org.ros.android_core:android_gingerbread_mr1:[0.1,0.2)'
    compile 'org.ros.android_core:android_honeycomb_mr2:[0.1,0.2)'
    compile 'org.ros.rosjava_core:rosjava:[0.1,0.2)'
}

I updated the wiki to reflect this. Try that and let me know how it goes.

Also note that in general, I try to keep the hydro release branch working and up to date the with the latest version of Android Studio (as of this moment, 0.6.1). The upgrades tend to always require newer versions of gradle, the android gradle plugin and the sdk build tools so when there is a studio update, we update the rosjava_bootstrap and rosjava_build_tools helpers to facilitate this. If you catch an upgrade before we do, send us a pull request (see the RosJava FAQ and Android FAQ for information on how to do so.

If you do want to keep building on old versions of android studio, you can always lock down the appropriate version variables in your build.gradle.

I just saw the wiki documentation for that is using the ivy style for open ranged dependencies. If you're using the maven repo directly, you need the maven style format (refer to this issue thread). That is,

dependencies {
    compile 'org.ros.android_core:android_gingerbread_mr1:0.1.+'
    compile 'org.ros.android_core:android_honeycomb_mr2:0.1.+'
    compile 'org.ros.rosjava_core:rosjava:0.1.+'
}

should be

dependencies {
    compile 'org.ros.android_core:android_gingerbread_mr1:[0.1,0.2)'
    compile 'org.ros.android_core:android_honeycomb_mr2:[0.1,0.2)'
    compile 'org.ros.rosjava_core:rosjava:[0.1,0.2)'
}

I updated the wiki to reflect this. Try that and let me know how it goes.

Also note that in general, I try to keep the hydro release branch working and up to date the with the latest version of Android Studio (as of this moment, 0.6.1). The upgrades tend to always require newer versions of gradle, the android gradle plugin and the sdk build tools so when there is a studio update, we update the rosjava_bootstrap and rosjava_build_tools helpers to facilitate this. If you catch an upgrade before we do, send us a pull request (see the RosJava FAQ and Android FAQ for information on how to do so.so).

If you do want to keep building on old versions of android studio, you can always lock down the appropriate version variables in your build.gradle but we don't have the man-hours to support this officially in the releases.