Russel Winder wrote:
Thi relates to Trunk as at 2009-04-19 07:00:00+01:00.
I wonder if there is a way of making the output from "gradle -t" a
little less "messy". I find the output difficult to read quickly and
quick reading is what this should offer. I wonder if the problem is
having the dependencies on a line following the entry indented, e.g.:
:processTestResources - Process and copy the test resources into the binary
directory of the compiled test sources.
-> :compile
I wonder if this might work better as:
:processTestResources [ :compile ] -- Process and copy the test resources into
the binary directory of the compiled test sources.
i.e if there are dependencies then use a list in brackets following the
task name, if there are no dependencies then print nothing, not even the
brackets.
I think that since this most often ends up with wrapped lines in my shell it
actually looks better as is. From the java multiproject sample (first 10 tasks):
Your proposal (wrapped to 80 columns):
:api:archive_jar [:api:test, :shared:archive_jar]- Generates a jar archive with
all the compiled classes.
:api:archive_spi_jar [:api:test]
:api:archive_zip [:api:libs, :shared:uploadDefaultInternal]
:api:clean [:shared:clean]- Deletes the build directory.
:api:compile [:api:processResources, :shared:compile, :shared:uploadDefaultInter
nal]- Compiles the Java source code.
:api:compileTests [:api:processTestResources, :shared:compileTests, :shared:uplo
adDefaultInternal]- Compiles the Java test source code.
:api:dists [:api:archive_zip, :api:libs, :shared:dists]
:api:eclipse [:api:eclipseCp, :api:eclipseProject, :shared:eclipse]- Generates a
n Eclipse .project and .classpath file.
:api:eclipseClean [:shared:eclipseClean]- Deletes the Eclipse .project and .clas
spath files.
:api:eclipseCp [:shared:eclipseCp]- Generates an Eclipse .classpath file.
Current (wrapped to 80 columns):
:api:archive_jar - Generates a jar archive with all the compiled classes.
-> :api:test, :shared:archive_jar
:api:archive_spi_jar
-> :api:test
:api:archive_zip
-> :api:libs, :shared:uploadDefaultInternal
:api:clean - Deletes the build directory.
-> :shared:clean
:api:compile - Compiles the Java source code.
-> :api:processResources, :shared:compile, :shared:uploadDefaultInternal
:api:compileTests - Compiles the Java test source code.
-> :api:processTestResources, :shared:compileTests, :shared:uploadDefaultInte
rnal
:api:dists
-> :api:archive_zip, :api:libs, :shared:dists
:api:eclipse - Generates an Eclipse .project and .classpath file.
-> :api:eclipseCp, :api:eclipseProject, :shared:eclipse
:api:eclipseClean - Deletes the Eclipse .project and .classpath files.
-> :shared:eclipseClean
:api:eclipseCp - Generates an Eclipse .classpath file.
-> :shared:eclipseCp
What I find annoying is that the handy taskReport task from the project-reports
plugin only sends output to a text file in the build folder. I wish it went to
stdout too. I find that I most often just need to get a task or dependencies
report for a single project and I can't look at the response conveniently from
the command line. We have 40 projects in our current build and the output from
gradle -t is 1750 lines long.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
