diff --git a/docs/antnews.html b/docs/antnews.html index e3bfaaddc..6446c9b92 100644 --- a/docs/antnews.html +++ b/docs/antnews.html @@ -25,7 +25,7 @@ - + Apache Ant @@ -103,9 +103,12 @@

Mar 26, 2002: Ant wins the JavaWorld Editors' Choice - award

-

Ant has won the JavaWorld Editors' Choice award for - "Most Useful Java Community-Developed Technology".

+ Award +

Ant has won the JavaWorld Editors' Choice Award for + Most Useful Java Community-Developed Technology. + Read the + full article -- or jump directly to the bit about + our award :)

diff --git a/docs/external.html b/docs/external.html index b2ff92839..ddbd76eb3 100644 --- a/docs/external.html +++ b/docs/external.html @@ -23,7 +23,7 @@ - + Apache Ant diff --git a/docs/faq.html b/docs/faq.html index 000286a7e..87a7b0fa0 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -23,7 +23,7 @@ - + Apache Ant diff --git a/docs/images/jw_ec_logo_finalist2002.gif b/docs/images/jw_ec_logo_finalist2002.gif deleted file mode 100644 index 68a4e41e3..000000000 Binary files a/docs/images/jw_ec_logo_finalist2002.gif and /dev/null differ diff --git a/docs/images/jw_ec_logo_winner2002.gif b/docs/images/jw_ec_logo_winner2002.gif new file mode 100644 index 000000000..334b1146b Binary files /dev/null and b/docs/images/jw_ec_logo_winner2002.gif differ diff --git a/docs/index.html b/docs/index.html index 880200277..29e9ca271 100644 --- a/docs/index.html +++ b/docs/index.html @@ -25,7 +25,7 @@ - + Apache Ant @@ -103,8 +103,9 @@

We are proud to announce that Ant has won the JavaWorld - Editors' Choice award for "Most Useful Java - Community-Developed Technology"

+ Editors' Choice Award for Most Useful Java + Community-Developed Technology. Click on the "News" link + to learn more.

@@ -134,15 +135,16 @@

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

-Why another build tool when there is already make, gnumake, nmake, jam, and -others? Because all of those tools have limitations that Ant's original author +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 and then -execute commands not unlike what you would issue on a shell. This means that you +tools are inherently shell-based -- they evaluate a set of dependencies, then +execute commands not unlike what you would issue in 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. @@ -152,20 +154,22 @@ 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 use yet another format to use and remember. +still have yet another format to use and remember.

-Ant is different. Instead of a model where it is extended with shell based -commands, it 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 which implements a particular +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 by 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 rule that +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 that it is executing on.

diff --git a/docs/problems.html b/docs/problems.html index f89826e1d..035284b79 100644 --- a/docs/problems.html +++ b/docs/problems.html @@ -23,7 +23,7 @@ - + Apache Ant @@ -179,13 +179,13 @@ Complete build sequence is [debug, gensrc, compile, jar, test]
You should be able to see from the trace more about what Ant is doing and why it's taking a particular course of action. If you need even more information, you can use the - -debug flag rather than - -verbose. + -debug flag rather than + -verbose. This will generally produce so much output that you may want to save the output to a file and analyze it in an editor. You can save the output using the - -logfile <filename> flag, or using - redirection. + -logfile <filename> flag, or + using redirection.

Once you have all this debug information, how can you use it @@ -309,7 +309,8 @@ D:\src\java\Unset.java

By this time, you may have decided that there is an unreported bug in Ant. You have a few choices at this point. You can send - an email to the ant-user mailing list to see if + an email to the ant-user mailing list + to see if others have encountered your issue and find out how they may have worked around it. If after some discussion, you feel it is time to create @@ -385,18 +386,20 @@ D:\src\java\Unset.java
source distributions. If you are going to tackle the problem at this level, you may want to - discuss some details first on the ant-dev mailing - list. Once you have a fix for the problem, you may submit - the fix as a patch to either the ant-dev mailing + discuss some details first on the ant-dev + mailing list. Once you have a fix for the problem, you may submit + the fix as a patch to either the + ant-dev mailing list, or enter the bug database as described above and attach the patch to the bug report. Using the bug database has the advantage of being able to track the progress of your patch.

If you have a patch to submit and are sending it to the - ant-dev mailing list, prefix "[PATCH]" + ant-dev mailing list, + prefix "[PATCH]" to your message subject. Please include any relevant bug numbers. - Patch files should be created with the -u + Patch files should be created with the -u option of the diff or cvs diff command. For example:

diff --git a/docs/projects.html b/docs/projects.html index 7afadbb08..d93f07129 100644 --- a/docs/projects.html +++ b/docs/projects.html @@ -23,7 +23,7 @@ - + Apache Ant diff --git a/docs/resources.html b/docs/resources.html index bb075a2b2..b25bafce3 100644 --- a/docs/resources.html +++ b/docs/resources.html @@ -23,7 +23,7 @@ - + Apache Ant diff --git a/xdocs/antnews.xml b/xdocs/antnews.xml index cdcae6876..b69832179 100644 --- a/xdocs/antnews.xml +++ b/xdocs/antnews.xml @@ -10,10 +10,14 @@

Mar 26, 2002: Ant wins the JavaWorld Editors' Choice - award

+ Award -

Ant has won the JavaWorld Editors' Choice award for - "Most Useful Java Community-Developed Technology".

+

Ant has won the JavaWorld Editors' Choice Award for + Most Useful Java Community-Developed Technology. + Read the + full article -- or jump directly to the bit about + our award :)

diff --git a/xdocs/index.xml b/xdocs/index.xml index 3bfacc3cd..76684751a 100644 --- a/xdocs/index.xml +++ b/xdocs/index.xml @@ -11,8 +11,9 @@

We are proud to announce that Ant has won the JavaWorld - Editors' Choice award for "Most Useful Java - Community-Developed Technology"

+ Editors' Choice Award for Most Useful Java + Community-Developed Technology. Click on the "News" link + to learn more.

@@ -27,16 +28,17 @@

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

-Why another build tool when there is already make, gnumake, nmake, jam, and -others? Because all of those tools have limitations that Ant's original author +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 and then -execute commands not unlike what you would issue on a shell. This means that you +tools are inherently shell-based -- they evaluate a set of dependencies, then +execute commands not unlike what you would issue in 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. @@ -47,22 +49,24 @@ 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 use yet another format to use and remember. +still have yet another format to use and remember.

-Ant is different. Instead of a model where it is extended with shell based -commands, it 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 which implements a particular +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 by 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 rule that +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 that it is executing on.

diff --git a/xdocs/problems.xml b/xdocs/problems.xml index d1c577435..a6b9fae2e 100644 --- a/xdocs/problems.xml +++ b/xdocs/problems.xml @@ -67,13 +67,13 @@ Complete build sequence is [debug, gensrc, compile, jar, test]

You should be able to see from the trace more about what Ant is doing and why it's taking a particular course of action. If you need even more information, you can use the - -debug flag rather than - -verbose. + -debug flag rather than + -verbose. This will generally produce so much output that you may want to save the output to a file and analyze it in an editor. You can save the output using the - -logfile <filename> flag, or using - redirection. + -logfile <filename> flag, or + using redirection.

Once you have all this debug information, how can you use it @@ -169,7 +169,8 @@ D:\src\java\Unset.java

By this time, you may have decided that there is an unreported bug in Ant. You have a few choices at this point. You can send - an email to the ant-user mailing list to see if + an email to the ant-user mailing list + to see if others have encountered your issue and find out how they may have worked around it. If after some discussion, you feel it is time to create @@ -229,18 +230,20 @@ D:\src\java\Unset.java

source distributions. If you are going to tackle the problem at this level, you may want to - discuss some details first on the ant-dev mailing - list. Once you have a fix for the problem, you may submit - the fix as a patch to either the ant-dev mailing + discuss some details first on the ant-dev + mailing list. Once you have a fix for the problem, you may submit + the fix as a patch to either the + ant-dev mailing list, or enter the bug database as described above and attach the patch to the bug report. Using the bug database has the advantage of being able to track the progress of your patch.

If you have a patch to submit and are sending it to the - ant-dev mailing list, prefix "[PATCH]" + ant-dev mailing list, + prefix "[PATCH]" to your message subject. Please include any relevant bug numbers. - Patch files should be created with the -u + Patch files should be created with the -u option of the diff or cvs diff command. For example:



diff --git a/xdocs/stylesheets/templates.vm b/xdocs/stylesheets/templates.vm index cb1256545..7e7219891 100644 --- a/xdocs/stylesheets/templates.vm +++ b/xdocs/stylesheets/templates.vm @@ -130,7 +130,7 @@ - + #set ( $logoString = $project.getChild("logo").getAttributeValue("href") )