This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Builders
May/June 2008 (vol. 25 no. 3)
pp. 22-23
Diomidis Spinellis, Athens University of Economics and Business
The tools and processes we use to transform our system's source code into an application that we can deploy or ship have always been important, but nowadays they can mean the difference between success and failure. Software building's golden rule is that you should automate all build tasks. The most popular tool options for doing this are the facilities that your integrated development environment (IDE) provides, the various implementations of Make, and Apache Ant and Maven. Using an IDE can be problematic. Ant and Maven provide a portable solution for Java developers, while Make is more flexible and transparent. You can optimize the build process by appropriate dependency tracking and parallelization. Once an automated build process is in place, you can use it as a basis for continuous builds.
Index Terms:
build process, Ant, Make, Maven, tinderbox, dependency tracking, continuous integration
Citation:
Diomidis Spinellis, "Software Builders," IEEE Software, vol. 25, no. 3, pp. 22-23, May-June 2008, doi:10.1109/MS.2008.74
Usage of this product signifies your acceptance of the Terms of Use.