From 753a6c60f47f3ac4f270005b65e9d6481de8eb68 Mon Sep 17 00:00:00 2001 From: Ashlee Young Date: Fri, 23 Oct 2015 10:00:02 -0700 Subject: Adding maven and ant source trees Change-Id: I0a39b9add833a31b9c3f98d193983ae2f3a5a445 Signed-off-by: Ashlee Young --- .../src/ant/apache-ant-1.9.6/manual/intro.html | 69 ++++++++++++++++++++++ 1 file changed, 69 insertions(+) create mode 100644 framework/src/ant/apache-ant-1.9.6/manual/intro.html (limited to 'framework/src/ant/apache-ant-1.9.6/manual/intro.html') diff --git a/framework/src/ant/apache-ant-1.9.6/manual/intro.html b/framework/src/ant/apache-ant-1.9.6/manual/intro.html new file mode 100644 index 00000000..e5673ed7 --- /dev/null +++ b/framework/src/ant/apache-ant-1.9.6/manual/intro.html @@ -0,0 +1,69 @@ + + + + + + +Apache Ant User Manual - Introduction + + + +

Introduction

Apache Ant is a Java-based build tool. In theory, it is kind of like +make, without make's wrinkles.

Why?

Why another build tool when there is already +make, +gnumake, +nmake, +jam, +and +others? Because all those tools have limitations that Ant's original author +couldn't live with when developing software across multiple platforms. +Make-like +tools are inherently shell-based: they evaluate a set of dependencies, +then execute commands not unlike what you would issue on a shell. +This means that you +can easily extend these tools by using or writing any program for the OS that +you are working on; however, this also means that you limit yourself to the OS, +or at least the OS type, such as Unix, that you are working on.

Makefiles are inherently evil as well. Anybody who has worked on them for any +time has run into the dreaded tab problem. "Is my command not executing +because I have a space in front of my tab?!!" said the original author of +Ant way too many times. Tools like Jam took care of this to a great degree, but +still have yet another format to use and remember.

Ant is different. Instead of a model where it is extended with shell-based +commands, Ant is extended using Java classes. Instead of writing shell commands, +the configuration files are XML-based, calling out a target tree where various +tasks get executed. Each task is run by an object that implements a particular +Task interface.

Granted, this removes some of the expressive power that is inherent in being +able to construct a shell command such as +`find . -name foo -exec rm {}`, but it +gives you the ability to be cross-platform--to work anywhere and +everywhere. And +hey, if you really need to execute a shell command, Ant has an +<exec> task that +allows different commands to be executed based on the OS it is executing +on.

+ + + + + + -- cgit 1.2.3-korg