We are using a relatively early release of 0.9, so this might have been fixed.
Let's say I have a module that uses an external library (named foo). Foo also depends on a library (named Bar), as is indicated in it's POM. My module uses classes from both Foo and Bar libraries, and thus declares said dependencies. It looks like Gradle only notes the Foo dependency because Bar is available transitively through Foo. Every thing compiles just fine. But, when I try to generate javadocs I get an "unkown symbol" error for the classes defined in Bar. Is this a bug? Has it already been fixed? BTW, we worked around this by augmenting the javadoc classpath property with the projects transitive dependencies. Something like this (I don't have the code handy): javadoc.classpath += files(configurations.compile.copyRecursive(ProjectDependency.EXTERNAL).resolve()) Ugly and sometimes inefficient (has to resolve all the files even though it might not need them), but worked. -- John Murph Automated Logic Research Team
