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=10063>. 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=10063 Multiple Class-Path attributes in Manifest.MF not allowed by Ant. Summary: Multiple Class-Path attributes in Manifest.MF not allowed by Ant. Product: Ant Version: 1.4.1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] According to http://java.sun.com/docs/books/tutorial/ext/basics/download.html Multiple Class-Path entries in the manifest are allowed. In 1.4.1 (haven't tried 1.5b2 yet) doing <manifest> <attribute name="Class-Path" value="somejar.jar"/> <attribute name="Class-Path" value="anotherjar.jar"/> </manifest> in the <jar> task throws an error claiming that only one Class-Path per manifest is allowed. I couldn't find a reference to this limitation in the Manifest spec, but the tutorial says it's ok. The error is generated when ant runs. It would be really nice if the jar task had a lib sub-task like the war task that would place all jars in the META-INF/lib dir then include the entries in the Manifest.mf. Also the lib sub-task in war does not add entries to the manifest.mf in the war, don't know if this was spec or not, but the inconsistent behavior is confusing and should at least be documented in the Ant docs. Thanks, Curt -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
