|
|
|
@@ -305,7 +305,7 @@ |
|
|
|
<li><a href="#mangled-manifest"> |
|
|
|
|
|
|
|
Whenever I use the Ant jar or manifest related tasks, long lines in |
|
|
|
my manifest are wrapped at 70 characters and the resulting jar does |
|
|
|
my manifest are wrapped at 70 characters and the resulting jar does |
|
|
|
not work in my application server. Why does Ant do this? |
|
|
|
|
|
|
|
</a></li> |
|
|
|
@@ -739,12 +739,12 @@ Apache Ant version 1.6.2 compiled on July 16 2004 |
|
|
|
<a name="create-extensions"></a> |
|
|
|
How do I create new tasks? |
|
|
|
</p> |
|
|
|
<p>Apart from a lot of information on using Ant, the |
|
|
|
<a href="manual/index.html">Manual</a> also contains information |
|
|
|
on how to extend Ant with new tasks. This information |
|
|
|
<p>Apart from a lot of information on using Ant, the |
|
|
|
<a href="manual/index.html">Manual</a> also contains information |
|
|
|
on how to extend Ant with new tasks. This information |
|
|
|
can be found under "Developing with Ant".</p> |
|
|
|
<p>Chances are that someone else already created the task you |
|
|
|
want to create, it may be wise to see |
|
|
|
want to create, it may be wise to see |
|
|
|
<a href="external.html">External Tools and Tasks</a> and |
|
|
|
<a href="projects.html">Related Projects</a> first.</p> |
|
|
|
<p class="faq"> |
|
|
|
@@ -1260,28 +1260,28 @@ shell-prompt> m4 foo.m4 > foo |
|
|
|
<a name="mangled-manifest"></a> |
|
|
|
|
|
|
|
Whenever I use the Ant jar or manifest related tasks, long lines in |
|
|
|
my manifest are wrapped at 70 characters and the resulting jar does |
|
|
|
my manifest are wrapped at 70 characters and the resulting jar does |
|
|
|
not work in my application server. Why does Ant do this? |
|
|
|
|
|
|
|
</p> |
|
|
|
<p> |
|
|
|
Ant implements the Java |
|
|
|
<a href="http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html">Jar |
|
|
|
file specification</a>. Please refer to the notes section where it |
|
|
|
Ant implements the Java |
|
|
|
<a href="http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html">Jar |
|
|
|
file specification</a>. Please refer to the notes section where it |
|
|
|
discusses the maximum allowable length of a line and the concept of |
|
|
|
continuation characters. |
|
|
|
</p> |
|
|
|
<p> |
|
|
|
If a jar file produced by Ant does not work in your appserver, and |
|
|
|
If a jar file produced by Ant does not work in your appserver, and |
|
|
|
that failure is due to the wrapped manifest, then you need |
|
|
|
to consult your appserver provider, as it is a bug in their |
|
|
|
appserver. Far more likely, however, is a problem in your |
|
|
|
to consult your appserver provider, as it is a bug in their |
|
|
|
appserver. Far more likely, however, is a problem in your |
|
|
|
specification of your classpath. It is not Ant's wrapping of your |
|
|
|
classpath that is the problem. |
|
|
|
</p> |
|
|
|
<p> |
|
|
|
Do not raise a bug about this issue until you have checked to ensure |
|
|
|
that the problem is not due to your classpath specification. |
|
|
|
Do not raise a bug about this issue until you have checked to ensure |
|
|
|
that the problem is not due to your classpath specification. |
|
|
|
</p> |
|
|
|
<p class="faq"> |
|
|
|
<a name="integration"></a> |
|
|
|
@@ -1814,7 +1814,7 @@ mv /tmp/foo $ANT_HOME/bin/antRun |
|
|
|
<code>ant-xalan1.jar</code> or <code>ant-xslp.jar</code> - |
|
|
|
depending on the processor you use.</p> |
|
|
|
<p>If you do so, you will have to <code><taskdef></code> |
|
|
|
all optional tasks that need the external libary and use |
|
|
|
all optional tasks that need the external library and use |
|
|
|
nested <code><classpath></code> elements in the |
|
|
|
<code><taskdef></code> tasks that point to the new |
|
|
|
location of <code>ant-*.jar</code>. Also, don't forget |
|
|
|
|
Jan Materne