Ant learning notes

Ant learning notes

Author: Cha Dong

Summary: Ant is a Java-based automation scripting engine, the script format is XML. In addition to making Java compilation related tasks, Ant can also achieve a number of applications in a plugin. Basic Concepts 1) ANT is: 2) ANT installation: unpack, set the path 3) using ANT: The best way to learn is just a simple and practical example of the start ......: Cha Dong http: //www.chedong .com / tech / default.html

Basic Concept of Ant: Java's Makefile When a code project is big, it will become very complicated and repetitive each time, and there is a Make script in the C language to help these works. Application in Java is a platform-independent. Of course, these batch tasks are not completed with platform-related Make scripts. Ant itself is such a process scripting engine for automated calling programs to complete project compilation, packaging, test, etc. . In addition to Java-based platforms, the format of the script is based on XML, which is better to maintain than the Make script. A series of tasks (Target) is set in each Ant script (default build.xml): For example, there may be the following tasks for a general project.

Task 1: Usage Print this script Help information (Default) Task 2: Clean <- Init Clear Initialization Environment Task 3: Javadoc <- Build <- Init Generate Javadoc Task 4: Jar <- Build <- INIT generates JAR task 5: All <- jar javadoc <- build <- in j 完成 完成: JAR Javadoc often contains a certain dependency between multiple tasks: such as putting the entire application packaging task ( This is based on the compilation task, and the compilation task depends on the entire environment initialization task (INIT). Note: I see that the names in the Ant scripts in many projects are basically consistent, such as compilation. BUILD or Compile; package general call JAR or WAR; generate documents generally named javadoc or javadocs; Perform all task all. In each task, Ant will call some external applications according to the configuration and configure the corresponding parameters. Although Ant can call external applications very rich, it is actually 2,3: such as Javac Javadoc Jar et al. When the ANT is installed, add the path to the bin pointing to Ant in the system executable path, such as adding the following configuration on the GNU / Linux: Export Ant_Home = / Home / Antexport Java_Home = / USR / JAVA / J2SDK1.4.1EXPORT path = $ PATH: $ java_home / bin: $ ant_home / bin After performing Ant, if you do not specify the configuration file Ant will save the build.xml configuration file, and perform tasks according to the configuration file The default task settings can point to the most common tasks, such as: build, or pointing to print help: usage, telling users that there are those script options that can be used. Ant use

The best learning process is to understand the build.xml script in the Open source project, and then simplify into a simpler, Ant and Apache projects on Ant and Apache: Simple and easy to use, and adaptability is very Strong, because the establishment of these projects is often derived from the most direct needs of developers. The following is an example of a Weblucene application: Modify build.xml from JDOM:

< Property name = "debug" value = "OFF" />

============= -> generates The $ {name} .jar file "/> <

! - Prepares the Source Code -> < ! - CREATE DIRECTORIES ->

======================================================== - >

"$ {build.src}" /> Default task: USAGE print help documentation, Tell some task options: available for build, jar, javadoc, and clean. Initializing environment variable: INIT All tasks are based on the initialization of some basic environment variables, which is the basis of follow-up other tasks, in the environment initialization process, there are 2 Point comparison can be convenient to set: "/> Most simple configuration users can understand the build.properties, after all, XML is better than the key value attribute file or less readable. With build.properties, you can easily liberate from compiled details. 2 ClassPath Settings: Used in it:

It is equivalent to setting: classpath = / path / to / resin / lib / jsdk23.jar; / path / to / project / lib / *. Jar; file copy: pre previous-src creates a temporary src storage directory and output directory.

Compilation Task: Build ClassPath Environment When you find a reference to a PATH object

Package task: JAR writes the .jar file to the package generated project

Generate Javadoc document task: javadoc

============= -> Clearing temporary compilation file: clean

Todo: More task / extension: (sample)

Test Tasks: JUnit Test Code Style Check Tasks: Checkstyle, Jalopy and other email alerts: You can send the output warning of these tasks to the developed user list, this task can be set automatically. Reference: jakarta ant: http: //ant.apache.org/ Original source: http://www.chedong.com/tech/ant.html