Maybe you want to start with the "Hello World with Ant" tutorial [1] from 
the manual.
Have heard that the slides should be online. But havent found them yet. But
it would also easier and better to ask Steve directly - especially if you want
to reuse them. :)

The Wiki [2] contains some things which could be interesting for you. 


Jan

[1] http://ant.apache.org/manual/tutorial-HelloWorldWithAnt.html 
[2] http://wiki.apache.org/ant/AntOddities


>-----Ursprüngliche Nachricht-----
>Von: Andrew [mailto:[EMAIL PROTECTED] 
>Gesendet: Dienstag, 26. Juli 2005 08:17
>An: Ant Developers List
>Betreff: Re: Java Development with Ant
>
>I work in a web agency, here are some of the more esoteric 
>things I have done:
>
>- strictly control access to deployment/live servers; only 
>access to deploy is via a series of Ant tasks; limit files 
>that can go live by the use of file filters
>- promoting reference data from dev > staging databases
>- rename thousands of files according to certain glob patterns
>- auto-produce change logs (by invoking tools that analyse 
>cvs), including this as part of a release
>- extract a set of delta changes (between two cvs tags), zip 
>up as a "patch", scp to remote host
>- parse product catalogue files, convert into various XML 
>formats, dispatch by FTP to affiliate partners, record 
>success/fail in a database
>- invoking test scripts (note use of try/catch type Ant tasks)
>
>Some of the latter involved writing custom Ant tasks; this is 
>well worth the investment, generally - particularly if you 
>want to assure repeatable action (and hence quality) by 
>members of a team.  With careful use to always use relative 
>paths, a build.xml is totally portable between individual's 
>installations.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED] For 
>additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to