DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35209>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35209 Summary: WAR task manifest handling Product: Ant Version: 1.6.5 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: enhancement Priority: P2 Component: Core tasks AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] The WAR task should support the same nested manifest element as the JAR task. J2EE project builds may or may not need to include "Class-Path:" references in the WAR manifest.mf to access libraries contained under the EAR root. If not - a default manifest suffices, if so - an external manifest is required. The JAR task allows use of a specified external manifest AND a nested manifest element. This allows the external manifest to exist or not, depending on project requirements. WAR requires it's existence (if specified) and fails if not present. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
