Bug 18093 - <EAR> task proposed nested tasks to ease application.xml management
Summary: <EAR> task proposed nested tasks to ease application.xml management
Status: NEW
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: unspecified
Hardware: Other other
: P3 enhancement with 2 votes (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-18 08:46 UTC by Alberto Pizarro
Modified: 2008-11-24 03:57 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Pizarro 2003-03-18 08:46:28 UTC
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.