I think I understand the javadoc issues a little more, but still don't know
exactly what to do about it.
The java plugin doesn't seem to set up the classpath correctly for the javadoc
task.
Currently core:javadoc fails, but if I add
javadoc {
configuration = files(source.main.compileClasspath, source.main.classes)
}
to core.gradle, it works.
I copied this pattern from the root build.gradle, but I don't understand where
the configuration property of the JavaDoc task comes from. It seems like this
should be the classpath property, but if I don't set configuration it gives an
error. I don't see a setConfiguration in JavaDoc or any of its ancestors.
Should the output directory (source.main.classses) just be added to the
classpath convention in JavaPlugin.configureJavaDoc? I'm a little confused
about the connection between the classpath convention and the configuration
property.
I'm also confused about why running 'gradlew javadoc' runs javadoc on both the
root project and all the subprojects, but running 'gradlew explodedDist' which
depends on the root javadoc, does not run javadoc on the subprojects.
I guess I'm just all around confused this afternoon. Perhaps I just ate too
much lunch. I'll go get some coffee.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
