Graeme Rocher-4 wrote: > > I can't seem to work out how to produce a combined dependency report. >
Seems like it isn't supported yet and you'd have to merge the reports yourself. Graeme Rocher-4 wrote: > > Also it is fairly hard to work out what rendering options are > available since the javadoc and groovydoc links are broken: > > http://gradle.org/current/docs/javadoc/org/gradle/api/tasks/diagnostics/DependencyReportTask.html > I think it's because DependencyReportRenderer is an internal type. Our public API shouldn't reference such a type. Although it won't help you in this particular case, another good place to learn about configuration options is the DSL guide: http://gradle.org/current/docs/dsl/org.gradle.api.tasks.diagnostics.DependencyReportTask.html Graeme Rocher-4 wrote: > > How do I know what the subclasses of > org.gradle.api.tasks.diagnostics.internal.DependencyReportRenderer > are? > There is org.gradle.api.tasks.diagnostic.internal.AsciiReportRenderer and .GraphvizReportRenderer. I don't see a simple configuration option for the latter, but you should be able to set it as follows: dependencyReport { renderer = new org.gradle.api.tasks.diagnostic.internal.GraphvizReportRenderer() } This won't solve your merge problem though. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Blog: http://pniederw.wordpress.com Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/Combined-dependency-report-and-report-customization-tp4400434p4414138.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
