From d839298320ccb86d7f3dc29355e880c1c81323cb Mon Sep 17 00:00:00 2001
From: Steve Loughran <stevel@apache.org>
Date: Thu, 6 Jul 2006 09:00:14 +0000
Subject: [PATCH] some private emails about manifest correctness lead to more
 details on what to do if you disagree with the task's logic.

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@419490 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/CoreTasks/manifest.html | 33 ++++++++++++++++++-----------
 1 file changed, 21 insertions(+), 12 deletions(-)

diff --git a/docs/manual/CoreTasks/manifest.html b/docs/manual/CoreTasks/manifest.html
index 538ec0142..df00b914d 100644
--- a/docs/manual/CoreTasks/manifest.html
+++ b/docs/manual/CoreTasks/manifest.html
@@ -15,14 +15,7 @@
 <p>This task can be used to write a Manifest file, optionally
 replacing or updating an existing file.</p>
 
-<p>
-The Ant team regularly gets complaints that this task in generating invalid
-manifests. By and large, this is not the case: we believe that we are following
-the specification to the letter. The usual problem is that some third party
-manifest reader is not following the same specification as well as they think
-they should; we cannot generate invalid manifest files just because one
-single application is broken.
-</p>  
+
 
 <p>Manifests are processed according to the 
 <a href="http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html">Jar
@@ -32,6 +25,22 @@ attributes. Note in particular that this may result in manifest lines
 greater than 72 bytes being wrapped and continued on the next
 line.</p>
 
+<p>
+  The Ant team regularly gets complaints that this task in generating invalid
+  manifests. By and large, this is not the case: we believe that we are following
+  the specification to the letter. The usual problem is that some third party
+  manifest reader is not following the same specification as well as they think
+  they should; we cannot generate invalid manifest files just because one
+  single application is broken. J2ME runtimes appear to be particularly troublesome.
+</p>
+
+<p>
+  If you find that Ant generates manifests incompatible with your runtime, take
+  a manifest it has built, fix it up however you need and switch to using the &lt;zip&gt
+  task to create the JAR, feeding in the hand-crafted manifest.
+</p>
+
+
 
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
@@ -128,14 +137,14 @@ version identification</a> for the package <code>common</code>.</p>
 
 <pre><code>Manifest-Version: 1.0
 Built-By: bodewig
-Created-By: Apache Ant 1.5alpha
+Created-By: Apache Ant 1.7
 
 Name: common
 Specification-Title: Example
 Specification-Vendor: Example Organization
 Implementation-Vendor: Example Corp.
-Specification-Version: 1.1
-Implementation-Version: 1.1 February 19 2002
+Specification-Version: 1.2
+Implementation-Version: 1.2 February 19 2006
 Implementation-Title: common
 
 Name: common/class1.class
@@ -144,7 +153,7 @@ Sealed: false
 </code></pre>
 
 <hr>
-<p align="center">Copyright &copy; 2001-2005 The Apache Software Foundation. All rights
+<p align="center">Copyright &copy; 2001-2006 The Apache Software Foundation. All rights
 Reserved.</p>
 </body>
 </html>