Reading this, I started to wonder if a consistent color-coding of the
examples might help. I don't know if the way the docs are generated
support this but knowing at a glance which 'word' is a built-in call
(like dependencies) versus a task name versus a configuration name might
at least help.
...I may gen up some examples to illustrate what I'm talking about with
respect to clarity.
-Paul
Russel Winder wrote:
On Fri, 2009-12-11 at 08:37 -0800, Cédric Beust ♔ wrote:
For example, the first real example (5.4):
dependencies {
compile group: 'commons-collections', name: 'commons-collections', version:
'3.2'
testCompile group: 'junit', name: 'junit', version: '4.+'
}
What is compile? And testCompile? They are not explained before.
Actually, testCompile is never explained anywhere and that's the only
place it ever appears in the doc.
compile and testCompile are the names of configurations that are defined
in the Java plugin.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
