I small thought about messages to the user. I will raise a JIRA if that is appropriate. For a "missing task" invocation of Gradle I get:
|> gradle coverage
Build failed with an exception.
Run with -s or -d option to get more details. Run with -f option to get
the full (very verbose) stacktrace.
Task 'coverage' not found in root project 'ADS'.
BUILD FAILED
Total time: 4.154 secs
|>
A number of things:
-- the fact that the build failed with an exception is irrelevant to me
and as a user I don't even know what an exception is -- except that it
is clearly not something that should happen, it is an exception. This
creates stress.
-- As a user I am not going to be interested in stack traces. In fact
I may not even know what a stack trace is or how to use it. More
stress.
-- Aha now I get something I wanted and needed to know :-)
-- Ant started this highly non-Unix philosophy of printing out "BUILD
SUCCEEDED" or "BUILD FAILED" and the time it took. There has been some
discussion of this point associated with Gant, and the overall decision
is not not print this by default. I prefer the Unix philosophy to the
Ant approach.
-- As a corollary to the above, I wonder if printing out the phases
should not be the default? (This is probably more contentious.)
--
Russel.
============================================================
Dr Russel Winder Partner
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip:
sip:[email protected]
London SW11 1EN, UK. m: +44 7770 465 077 xmpp: [email protected]
signature.asc
Description: This is a digitally signed message part
