ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ste...@apache.org
Subject svn commit: r419490 - /ant/core/trunk/docs/manual/CoreTasks/manifest.html
Date Thu, 06 Jul 2006 09:00:14 GMT
Author: stevel
Date: Thu Jul  6 02:00:14 2006
New Revision: 419490

URL: http://svn.apache.org/viewvc?rev=419490&view=rev
Log:
some private emails about manifest correctness lead to more details on what to do if you disagree
with the task's logic.

Modified:
    ant/core/trunk/docs/manual/CoreTasks/manifest.html

Modified: ant/core/trunk/docs/manual/CoreTasks/manifest.html
URL: http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/CoreTasks/manifest.html?rev=419490&r1=419489&r2=419490&view=diff
==============================================================================
--- ant/core/trunk/docs/manual/CoreTasks/manifest.html (original)
+++ ant/core/trunk/docs/manual/CoreTasks/manifest.html Thu Jul  6 02:00:14 2006
@@ -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 @@
 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 @@
 
 <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 @@
 </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>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message