From 1bf93eb283281d1d964ceb5f5f29d4b7d5630749 Mon Sep 17 00:00:00 2001
From: Conor MacNeill <conor@apache.org>
Date: Wed, 15 Sep 2004 22:58:05 +0000
Subject: [PATCH] This is a FAQ by any measure.

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@276866 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/faq.html | 34 ++++++++++++++++++++++++++++++++++
 xdocs/faq.xml | 32 ++++++++++++++++++++++++++++++++
 2 files changed, 66 insertions(+)

diff --git a/docs/faq.html b/docs/faq.html
index 373f86d5e..79b3ec0b9 100644
--- a/docs/faq.html
+++ b/docs/faq.html
@@ -293,6 +293,13 @@
   I installed Ant 1.6.x and now get
         <code>java.lang.InstantiationException: org.apache.tools.ant.Main</code>
       
+      </a></li>
+                <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 
+        not work in my application server. Why does Ant do this?
+      
       </a></li>
             </ul>
                 <h4 class="toc">Ant and IDEs/Editors</h4>
@@ -1162,6 +1169,33 @@ shell-prompt&gt; m4 foo.m4 &gt; foo
                         <p>
           One can check if this is the case by doing
           <code>ant --noconfig -version</code>.
+        </p>
+                    <p class="faq">
+      <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 
+        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 
+          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 
+          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 
+          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.  
         </p>
                                 <p class="faq">
       <a name="integration"></a>
diff --git a/xdocs/faq.xml b/xdocs/faq.xml
index 97f1ac1b8..7dba002c0 100644
--- a/xdocs/faq.xml
+++ b/xdocs/faq.xml
@@ -845,6 +845,38 @@ shell-prompt> m4 foo.m4 > foo
         </p>
       </answer>
     </faq>
+    <faq id="mangled-manifest">
+      <question>
+        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 
+        not work in my application server. Why does Ant do this?
+      </question>
+      
+      <answer>
+        <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 
+          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 
+          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 
+          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.  
+        </p>
+      </answer>
+    </faq>
+      
   </faqsection>
 
   <faqsection title="Ant and IDEs/Editors">