conor       2004/09/15 15:58:05

  Modified:    docs     faq.html
               xdocs    faq.xml
  Log:
  This is a FAQ by any measure.
  
  Revision  Changes    Path
  1.108     +34 -0     ant/docs/faq.html
  
  Index: faq.html
  ===================================================================
  RCS file: /home/cvs/ant/docs/faq.html,v
  retrieving revision 1.107
  retrieving revision 1.108
  diff -u -w -u -r1.107 -r1.108
  --- faq.html  10 Sep 2004 16:52:23 -0000      1.107
  +++ faq.html  15 Sep 2004 22:58:05 -0000      1.108
  @@ -294,6 +294,13 @@
           <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>
           <ul>
  @@ -1162,6 +1169,33 @@
                           <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>
  
  
  
  1.63      +32 -0     ant/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/ant/xdocs/faq.xml,v
  retrieving revision 1.62
  retrieving revision 1.63
  diff -u -w -u -r1.62 -r1.63
  --- faq.xml   10 Sep 2004 16:52:22 -0000      1.62
  +++ faq.xml   15 Sep 2004 22:58:05 -0000      1.63
  @@ -845,6 +845,38 @@
           </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">
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to