[GRADLE-326] The dependencies introduced by the Java plugin should be documented with a dag diagram Created: 20/Dec/08  Updated: 04/Jan/13  Resolved: 28/Sep/09

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.8

Type: Bug
Reporter: Jon Cox Assignee: Hans Dockter
Resolution: Fixed Votes: 0


 Description   

It was a bit tricky figuring out what depended on what when I read the java plugin docs in the user manual
JIRA won't let me use a fixed-width font (which is inconvenient for code snippets & ascii art fans!),
so here's a linearized version:

clean
init - resources - compile - testResources - testCompile - test - archive_jar - libs
libs - uploadInternalLibs
libs - uploadLibs
libs - dists - uploadDists - upload
javadoc
eclipseCp
(javadoc,eclipseCP) - eclipse
eclipseClean
eclipseProject

Obviously, a pretty graphic would make things a lot nicer here!

I ended up using a bit of groovy to figure it out:

tasks.each { t ->
if ( ! t.value.dependsOn) println "$t.value"
else t.value.dependsOn.each

{ println "$t.value requires\t$it\n\n" }

}


Generated at Wed Jun 30 11:27:20 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.