This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: The ANT way to Groovienss, Gant and etc
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
it seem while there is an explanation of Groovy Blocks and Enclosures such as Practical ANT Scripting at IBM DW, every article explains how to script ANT the groovy way. I guess I will have translate.
Because closures can delay behavior defined until runtime we can use this as the control logic within our ANT build file.
naother new choice is Gant. What is Gant? Gant is a way to run Groovy defined ant targets within Groovy and thus avoid the ANT XML files completely. Well almost completely.
My thinking is if you were to use the Gant method you woudl use a simple ANT XML build file to encapsulate the targets and use ANT script task to call the gant script that does the control logic work of the build. In others words, a way to transition current ANT users to the new build file logic and structure.
Thus, now we have two main methods doing groovy tagging groovy stuff fin ANT XML files or two Gant methods, straight Gant or encapsulate Gant in a small ANT XML file. Right now Gant is so new that it does not work with current installs only from svn builds so if I go with groovy tagging the ANT XML file than I still have a transition path to Gant at a later date.
Previous Topic
