With Ant >= 1.5, you can also use nested
<compilerarg> elements with the
<javac> task.
| @@ -836,14 +806,11 @@ |
The short answer is "Use: <".
The long answer is that this probably won't do what you want anyway (see the next section).
- - - +| @@ -854,7 +821,6 @@ |
Say you want to redirect the standard input stream of the
cat command to read from a file, something
like:
Note the double-quotes nested inside the single-quotes.
- - - +| @@ -899,7 +863,6 @@ shell-prompt> cat < foo |
On native Unix systems, you should be able to run shell scripts
directly. On systems running a Unix-type shell (for example, Cygwin
on Windows) execute the (command) shell instead - cmd
@@ -915,9 +878,7 @@ shell-prompt> cat < foo
<arg line="/c test.bat"/>
</exec>
-
| @@ -928,7 +889,6 @@ shell-prompt> cat < foo |
There are actually several answers to this question.
If you have only one set and one unset property to test,
you can specify both an if and an unless
@@ -1029,9 +989,7 @@ shell-prompt> cat < foo
<script> task documentation for more
details.
| @@ -1042,7 +1000,6 @@ shell-prompt> cat < foo |
You need to tell the XML parser which character encoding your build file uses, this is done inside the XML declaration.
@@ -1054,9 +1011,7 @@ shell-prompt> cat < foo<?xml version="1.0" encoding="ISO-8859-1" ?>- - - +
| @@ -1066,7 +1021,6 @@ shell-prompt> cat < foo |
In order to find out which files should be compiled, Ant
compares the timestamps of the source files to those of the
resulting .class files. Opening all source files
@@ -1091,9 +1045,7 @@ shell-prompt> cat < foo
the actual directory the source
files live in and the directory the class files should go into,
respectively.
| @@ -1106,7 +1058,6 @@ shell-prompt> cat < foo |
This is probably happening because, by default, Ant excludes
SourceSafe control files (vssver.scc) and certain other
files from FileSets.
For a complete listing of the patterns that are excluded by default, see the user manual.
- - - +| @@ -1142,7 +1091,6 @@ shell-prompt> cat < foo |
The list of dependencies is generated by Ant before any of the
targets are run. This allows dependent targets, such as an
init target, to set properties that can control the
@@ -1160,9 +1108,7 @@ shell-prompt> cat < foo
instead of specifying them inside the depends
attribute.
-
| @@ -1176,7 +1122,6 @@ shell-prompt> cat < foo |
The order of the <include> and
<exclude> tags within a <fileset>
is ignored when the FileSet is created. Instead, all of the
@@ -1190,9 +1135,7 @@ shell-prompt> cat < foo
to get them. If you find you need to trim the list that the
<include> elements produce, then use
<exclude> elements.
| @@ -1205,7 +1148,6 @@ shell-prompt> cat < foo |
When ant loads properties from an external
file it dosn't touch the value of properties, trailing blanks
will not be trimmed for example.
| @@ -1227,7 +1167,6 @@ shell-prompt> cat < foo |
No it doesn't.
You may have seen these lower-case directory names in WinZIP, but WinZIP is trying to be helpful (and fails). If @@ -1236,9 +1175,7 @@ shell-prompt> cat < foo all lower-case for you.
If you extract (or just check) the archive with jar, you will see that the names have the correct case.
- - - +| @@ -1248,12 +1185,9 @@ shell-prompt> cat < foo |
See the section on IDE integration on our External Tools and Tasks page.
- - - +| @@ -1264,7 +1198,6 @@ shell-prompt> cat < foo |
Ant adds a "banner" with the name of the current task in front of all logging messages - and there are no built-in regular expressions in your editor that would account for @@ -1317,9 +1250,7 @@ while(<STDIN>) { print; }; -
- - +| @@ -1330,7 +1261,6 @@ while(<STDIN>) { |
An incomplete DTD can be created by the
<antstructure> task - but this one
has a few problems:
| @@ -1367,7 +1295,6 @@ while(<STDIN>) { |
You can use XML's way of including external files and let the parser do the job for Ant:
@@ -1397,9 +1324,7 @@ while(<STDIN>) {
<!ENTITY include SYSTEM "file:./header.xml">
]>
-
-
-
+
| @@ -1410,7 +1335,6 @@ while(<STDIN>) { |
If you are using a nightly build of Ant 1.5 after 2001-12-14, you can use the built-in MailLogger:
@@ -1564,9 +1488,7 @@ ant -listener BuildMonitor -logfile build.log
activation.jar from the
Java
Beans Activation Framework are in your CLASSPATH.
-
-
-
+
| @@ -1577,7 +1499,6 @@ ant -listener BuildMonitor -logfile build.log |
You can get at a hashtable with all the properties that Ant has been using through the BuildEvent parameter. For example:
@@ -1591,9 +1512,7 @@ public void buildFinished(BuildEvent e) {This is more accurate than just reading the same property files that your project does, since it will give the correct results for properties that were specified on the Ant command line.
- - - +| @@ -1604,7 +1523,6 @@ public void buildFinished(BuildEvent e) { |
The antRun script in ANT_HOME/bin
has DOS instead of Unix line endings; you must remove the
carriage-return characters from this file. This can be done by
@@ -1614,9 +1532,7 @@ public void buildFinished(BuildEvent e) {
tr -d '\r' < $ANT_HOME/bin/antRun > /tmp/foo
mv /tmp/foo $ANT_HOME/bin/antRun
-
| @@ -1626,14 +1542,11 @@ mv /tmp/foo $ANT_HOME/bin/antRun |
There is a bug in the Solaris reference implementation of the JDK (see http://developer.java.sun.com/developer/bugParade/bugs/4230399.html). This also appears to be true under Linux. Moving the JDK to the front of the PATH fixes the problem.
- - - +| @@ -1644,7 +1557,6 @@ mv /tmp/foo $ANT_HOME/bin/antRun |
These tasks don't ignore your classpath setting, you are facing a common problem with delegating classloaders.
First of all let's state that Ant adds all
@@ -1736,9 +1648,7 @@ mv /tmp/foo $ANT_HOME/bin/antRun
for <junit>, you still have to use a
<taskdef> with a nested
<classpath> to define the junit task.
| @@ -1751,7 +1661,6 @@ mv /tmp/foo $ANT_HOME/bin/antRun |
Ant < 1.5 doesn't recognize Windows XP as a flavor
of Windows that runs CMD.EXE instead of
COMMAND.COM. JDK 1.3 will tell Ant that Windows
@@ -1761,9 +1670,7 @@ mv /tmp/foo $ANT_HOME/bin/antRun
environment variable ANT_OPTS to
-Dos.name=Windows_NT prior to invoking Ant has
been confirmed as a workaround.
| @@ -1775,15 +1682,12 @@ mv /tmp/foo $ANT_HOME/bin/antRun |
This problem has been reported only hours after Ant 1.5 has been released, see Bug 10664 and all it's duplicates.
A fixed version of the wrapper script can be found here. Simply replace your script with this version.
- - - +
You can download the original license file here
+You can download the original license file here
diff --git a/proposal/ant-site/anakia/docs/mail.html b/proposal/ant-site/anakia/docs/mail.html index fbc1a61b1..c49b2eb62 100644 --- a/proposal/ant-site/anakia/docs/mail.html +++ b/proposal/ant-site/anakia/docs/mail.html @@ -206,12 +206,10 @@The user and dev list are subscriber only lists, this means you have to subscribe before you can post to the list. These lists are archived at
--
-
+
-
- The new Ant 1.5 features
- Ant's datatypes and property handling
- JUnit testing and reporting @@ -292,7 +292,6 @@
- Automated unit and functional testing
- Continuous integration through build and deployment automation
- The value of refactoring and continuous integration
- How Ant, JUnit, JUnitPerf, Cactus, HTTPUnit, and JMeter can be used to achieve the goals of the XP methodology
|
diff --git a/proposal/ant-site/anakia/docs/problems.html b/proposal/ant-site/anakia/docs/problems.html
index e366d3690..75a16a9e4 100644
--- a/proposal/ant-site/anakia/docs/problems.html
+++ b/proposal/ant-site/anakia/docs/problems.html
@@ -278,12 +278,12 @@ 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-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>-logfile <filename> flag, or
using redirection.
@@ -400,7 +400,7 @@ 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
If you have a patch to submit and are sending it to the
- |
Covers Ant 1.5, including: -
-
+
Covers Ant 1.5, including:
+A German language short reference for Ant that covers Ant
1.4. This is the original description:
- Ant kurz & gut enthält eine vollständige Referenz der Built-in Tasks - und ihrer jeweiligen Attribute sowie kurze Beispiele für ihre Verwendung. - Daneben bietet das Buch eine knappe Einführung in die Arbeit mit Ant und - eine Erläuterung der Ant-Basiselemente (Projekte, Properties, Targets und Tasks). - Behandelt werden außerdem grundlegende Konzepte wie Filesets, Patternsets und + Ant kurz & gut enth�lt eine vollst�ndige Referenz der Built-in Tasks + und ihrer jeweiligen Attribute sowie kurze Beispiele f�r ihre Verwendung. + Daneben bietet das Buch eine knappe Einf�hrung in die Arbeit mit Ant und + eine Erl�uterung der Ant-Basiselemente (Projekte, Properties, Targets und Tasks). + Behandelt werden au�erdem grundlegende Konzepte wie Filesets, Patternsets und Pfadstrukturen, das Schreiben eigener Tasks, die Aufruf-Syntax und Optional Tasks. This book covers the following XP subjects: -
This book covers the following XP subjects: +
|
|---|