DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5802>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5802 adding a manifest using <ejbjar> ------- Additional Comments From [EMAIL PROTECTED] 2002-01-21 08:28 ------- I had the same problem, but I think I found the solution. The EjbJar task uses the JDK java.util.jar.Manifest and related classes (the builtin "jar" task does not use this approach!). The Manifest class REQUIRES the attribute Manifest-Version: 1.0 If this attribute is not put in the main attributes of the manifest file, the Manifest instance generated from the file will not contain ANY attributes at all. This is reported as a bug/inconveniency in the JDK: http://developer.java.sun.com/developer/bugParade/bugs/4271239.html It took me quite a while to figure out what the problem was. Luckily, it does not require any changes to ant. By the way, remember that the manifest attributes are case-sensitive. All attributes in your manifest file that does not match case-sensitive one of the attribute keys given in java.util.jar.Attributes.Name will not be included in the final manifest file in the jar archive. Jesper Joergensen [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
