|
@@ -410,8 +409,7 @@
path.
-
-
+
-
The latest version can always be found at Ant's homepage
http://jakarta.apache.org/ant/faq.html.
-
+
+
|
@@ -451,7 +449,8 @@
If you don't know how to create a patch, see the patches
section of this
page.
-
+
+
@@ -473,7 +472,8 @@
well, but if you follow the instruction from Anakia's
homepage, you should get it to work without that. Just make
sure all required jars are in the task's classpath.
-
+
+
|
@@ -486,7 +486,8 @@
Ant is a Java-based build tool. In theory, it is kind of
like Make, without Make's wrinkles and with the full
portability of pure Java code.
-
+
+
@@ -504,7 +505,8 @@
"ants are very small and can carry a weight dozens of times
their own" - describing what Ant is intended to
be.
-
+
+
-
+
+
@@ -641,7 +644,8 @@
found here,
or use the zip archive instead (you can extract it using
jar xf).
-
+
+
|
@@ -672,7 +676,8 @@
The preferred format for this information is a patch to this
document.
-
+
+
@@ -689,7 +694,8 @@
used within your build file as
any normal property: ${name} will put in
value.
-
+
+
|
@@ -780,7 +786,8 @@
With Ant >= 1.5, you can also use nested
<compilerarg> elements with the
<javac> task.
-
+
+
|
@@ -794,7 +801,8 @@
The long answer is that this probably won't do what you
want anyway (see the next
section).
-
+
+
|
@@ -837,7 +845,8 @@ shell-prompt> cat < foo
</exec>
Note the double-quotes nested inside the single-quotes.
-
+
+
@@ -862,7 +871,8 @@ shell-prompt> cat < foo
<arg line="/c test.bat"/>
</exec>
-
+
+
@@ -973,7 +983,8 @@ shell-prompt> cat < foo
<script> task documentation for more
details.
-
+
+
@@ -995,7 +1006,8 @@ shell-prompt> cat < foo
<?xml version="1.0" encoding="ISO-8859-1" ?>
-
+
+
@@ -1029,7 +1041,8 @@ shell-prompt> cat < foo
the actual directory the source
files live in and the directory the class files should go into,
respectively.
-
+
+
|
@@ -1062,7 +1075,8 @@ shell-prompt> cat < foo
For a complete listing of the patterns that are excluded
by default, see the user
manual.
-
+
+
@@ -1092,7 +1106,8 @@ shell-prompt> cat < foo
instead of specifying them inside the depends
attribute.
-
+
+
@@ -1119,7 +1134,8 @@ 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.
-
+
+
@@ -1139,7 +1155,8 @@ shell-prompt> cat < foo
compile, the task which requires the value, javac for example
would fail to compile since it can't find the file due to
trailing spaces.
-
+
+
|
@@ -1159,7 +1176,8 @@ 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.
-
+
+
|
@@ -1171,7 +1189,8 @@ shell-prompt> cat < foo
|
See the section
on IDE integration on our External Tools and Tasks page.
-
+
+
@@ -1234,7 +1253,8 @@ while(<STDIN>) {
print;
};
-
+
+
@@ -1269,7 +1289,8 @@ while(<STDIN>) {
lists. This problem cannot be solved; DTDs don't give a
syntax rich enough to support this.
-
+
+
@@ -1308,7 +1329,8 @@ while(<STDIN>) {
<!ENTITY include SYSTEM "file:./header.xml">
]>
-
+
+
@@ -1472,7 +1494,8 @@ ant -listener BuildMonitor -logfile build.log
activation.jar from the
Java
Beans Activation Framework are in your CLASSPATH.
-
+
+
|
@@ -1496,7 +1519,8 @@ 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.
-
+
+
@@ -1516,7 +1540,8 @@ public void buildFinished(BuildEvent e) {
tr -d '\r' < $ANT_HOME/bin/antRun > /tmp/foo
mv /tmp/foo $ANT_HOME/bin/antRun
-
+
+
@@ -1530,7 +1555,8 @@ mv /tmp/foo $ANT_HOME/bin/antRun
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.
-
+
+
@@ -1632,7 +1658,8 @@ 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.
-
+
+
@@ -1654,7 +1681,8 @@ 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.
-
+
+
|
@@ -1671,8 +1699,8 @@ mv /tmp/foo $ANT_HOME/bin/antRun
10664 and all it's duplicates.
A fixed version of the wrapper script can be found here.
Simply replace your script with this version.
-
-
+
+
|  |
diff --git a/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl b/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl
index 3e2ccaa58..fb0de2aba 100644
--- a/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl
+++ b/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl
@@ -162,6 +162,7 @@
$xmlout.outputString($item)
#end
#end
+
#end
#macro (document)
@@ -187,11 +188,9 @@
-
#foreach ( $faqSection in $allFaqSections )
#toc ($faqSection)
#end
-
-
#foreach ( $faqSection in $allFaqSections )
#answers ($faqSection)
#end
-
#end
#footer()
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |