genjava and actionlib. Error generating action messages
Hi,
I'm using genjava from debs to build a package that includes actions as described in the tutorials: http://wiki.ros.org/rosjava/Tutorials/indigo/RosJava%20Message%20Artifacts
This has worked fine for me until recently. A couple of days ago I've installed ros Indigo in a new pc and when trying to compile that package, I get the following error:
What went wrong:
Could not resolve all dependencies for configuration ':runtime'.
Could not find org.ros.rosjava_messages:actionlib:1.11.6.
Searched in the following locations:
https://github.com/rosjava/rosjava_mvn_repo/raw/master/org/ros/rosjava_messages/actionlib/1.11.6/actionlib-1.11.6.pom
https://github.com/rosjava/rosjava_mvn_repo/raw/master/org/ros/rosjava_messages/actionlib/1.11.6/actionlib-1.11.6.jar
.....
.....
It seems that the autogenerated 'build.gradle' file for that package in the 'build' folder contains the following dependency that should not be there:
dependencies {
compile 'org.ros.rosjava_bootstrap:message_generation:[0.2,0.3)'
compile 'org.ros.rosjava_messages:actionlib:1.11.6' <================ THIS!!!!!!!!!
compile 'org.ros.rosjava_messages:roscpp:1.11.20'
compile 'org.ros.rosjava_messages:std_msgs:0.5.10'
compile 'org.ros.rosjava_messages:actionlib_msgs:1.11.9'
}
If I remove that line and compile the project with ./gradlew everything is generated as it should.
Searching for an answer, I've read that there has recently been an update of the actionlib. Maybe there is a mismatch between genjava and the new actionlib package? Is there a way to patch this without having to manualy delete that line each time I compile the package?
many thanks in advance.
Asked by sammar on 2016-08-25 02:11:48 UTC
Comments
No mismatch, but the maven repository just doesn't seem to have been updated with
1.11.6
(see here). Perhaps report at the issue tracker?Asked by gvdhoorn on 2016-08-25 04:20:39 UTC
Yeah, you're right. I've already done so. Thanks for your prompt response.
While this gets fixed, is there a workaround so as not to edit the 'build.gradle' each time I compile the package?
Thanks and best regards.
Asked by sammar on 2016-08-25 07:02:05 UTC
Looks like it is still broken.
Asked by Will Chamberlain on 2016-11-02 00:26:50 UTC