From CitconWiki
Revision as of 13:16, 21 September 2009 by (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Tip of the session: in order to "unit test" your common Ant scripts, have a test project that you can run the scripts against. You can then assert that the required artifacts are created as expected.

There was a discussion by Joe of the Ant Script Library, an open source library of re-usable build targets

Jeff pointed out a similar library in this area: the Ant Master Build Scripts. The author of these scripts also presented a talk at JavaOne called Object Oriented Ant Scripts for the Enterprise

Ivan talked about the problem of putting too much programming logic into build scripts, and looked for input about the best way to avoid this problem. Jeff suggested that choreographing complex logic in Ant is probably best done inside a custom Ant task, instead of trying to set up targets, or using Ant Contrib.

Bonus discussion: string literals are not always bad! For example: people often use a property for the directory containing all the library jars, calling it something like "library.dir", which means it must be referred to as "${library.dir}" where ever it is used. This is a lot harder than just typeing "lib", which is where pretty much everyone puts their jars, anyway!

Julian blogged. Joe blogged.