According to Sun's Jar file spec, it can be called a Jar file ;-) However, according to Sun's code and 'Java in a Nutshell', the Manifest needs to be the first entry.
Conor, I do understand your point and will address it (hopefully before beta3 tomorrow). Cheers, Magesh ********************************************* * Last night I played a blank tape at full * * blast. The mime next door went nuts. * ********************************************* ----- Original Message ----- From: "Conor MacNeill" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Friday, June 21, 2002 3:02 AM Subject: Jar issues > I have fixed the bugs regarding the regeneration of jars with inline > manifests. I have made the default to merge manifests. This will result > in the return of the Created-By header in jar manifests. > > In a somewhat related topic, I'm still concerned by this behaviour > > "Note: if this attribute's value is not "skip", the created jar will not > be readable by using java.util.jar.JarInputStream" > > I just don't think you could call such a result a jar. This is > especially the case since the end consumer of the jar may not be using > Ant and may not be aware of this caveat. > > Thoughts? > Conor > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
