Adam, On Fri, 2008-10-10 at 11:15 +1100, Adam Murdoch wrote:
> We have plugins and tasks as the Gradle-provided general mechanisms > for reuse (ignoring the fact that groovy is one giant reuse > mechanism). I guess the question is how to structure tasks. In Gant you can include Gant files within other Gant files so this is source code inclusion -- this gives very simple target (aka task) structuring. Gant doesn't have plugins per se but you can include precompiled classes which have an instantiation that allows them to manipulate the global state and so can appear as classic plugin type things or they can just create new targets. I am sure Gradle has fundamentally the same thing it is a question of mapping Gant idioms to Gradle idioms and not reinventing things. > BTW, I had a (really quick) look for some docs on Gant target sets, > but couldn't find any. Can you point me at some? Probably not as I am not sure there is any :-( This then leads to classic (but still awful) comment of "read the source code" ;-) Sorry but the Clean and Maven classes are the only target sets there are ready-made and they are not really finished. The Execute and Subdirectory tools are the only real ready-made tools and they are not really finished either. As you can tell I haven't really finished the architecture so hadn't got round to documenting things. -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
