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=18093>. 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=18093 <EAR> task proposed nested tasks to ease application.xml management Summary: <EAR> task proposed nested tasks to ease application.xml management Product: Ant Version: 1.5.1 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Current <EAR> task could more expression ability by adding specific NESTED TASKS, so that most of the information to use on application.xml could be automatically appended. The basis is that application.xml contains basically an INDEX description of the EAR file content, with some added value (security constraints, java/ejb/web classification, ...). Unfortunately, user which uses current <EAR> tasks must supply an application.xml which already contains this INDEX information, although filesets must be specified in order to comply with its applicacion.xml. Following the application.xml DTD we could have: <ear ..> <module> <java dir="...."> <-- fileset of java modules to add </module> ... <module> <ejb dir="..."> <--- fileset of EJB modules to add </module> ... <module> <web uri="..." context="..." file="..."> <-- maybe a single file </module> ... </ear> (Well, it is just a draft) With this information, it is easy to append module descriptions to an existing application.xml.
