One of the things you can look at is the use of property files to set
most of the variables in your various deployment environments.
You can then use the
in your Ant script to read in these properties, and then handle the
script based upon those properties.
Another feature of Ant is the abilit
Thanks to all for the information, but i haven´t seen anything helpful
refered to what i want to do in the links. Maybe I haven´t explain myself
very well, i give you my context.
I have all my apllications or most of them in .war filetype and running on
tomcat. Develop Department, give me the appl
Similarly, I've also just released some Ant library scripts here:
http://www.exubero.com/asl/
These are just build plugins which you can either import directly in your
own build, or just look over them as an example of how to write re-usable
Ant modules.
Cheers,
Joe
On Thu, March 5, 2009 3:44 p
The way to accomplish this with Ant is to use statements to
include common build files or use the -f flag to specify a common
build file for all the projects. However, if these solutions don't
meet your needs you can also take a look at other solutions like these:
- Gradle
- Maven
-
I would suggest that you take a look at Gant http://gant.codehaus.org/ which
allows for much more dynamic coding of Ant processes. This way you might be
able to get away with just a few Ant builds that are based on configurations.
In addition you will have direct access to Groovy which is a gr
