ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12960] - PropertyFile functionality for XMLProperty
Date Tue, 24 Sep 2002 15:56:41 GMT
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=12960>.
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=12960

PropertyFile functionality for XMLProperty





------- Additional Comments From dan.gardner@emap.com  2002-09-24 15:56 -------
I have not yet worked this out in my head.  I was thinking of a very simple, 
almost flat XML structure.  Feel free to can this if you have already been down 
this root, and it gets nasty.

The driving force behind this sugestion was as follows:

I maintain a PropertyFile of patches and order to apply:

patch1.name:p20020813_r2_v2_p1
patch1.description:bla bla bla bla bla
patch2.name:p20020924_r2_v2_p1
patch2.description:bla bla bla bla bla
patch3.name:p20020924_r2_v2_p2
patch3.description:bla bla bla bla bla

etc.

We use this to apply patches to a paticular release

1 pull from CVS where tag = r2
2 pull from CVS where tag = p20020813_r2_v2_p1
3 pull from CVS where tag = p20020924_r2_v2_p1
4 pull from CVS where tag = p20020924_r2_v2_p2
5 apply patches to release in corect order.

The build file currently has lots of repeated targets for a predefined number 
of patches.  I am looking at applying an XSLT to the build file in order to 
dynamically generate the targets based on how many patches need to be applied.  
This removes the number-of-patches ceiling on my current build file.

If I could maintain the patch list in an XML format, then I could apply an XSLT 
to it (dynamically building the nessasary targets for each patch), and import 
the result into my build file.

This would give a task structure something like:

<XMLPropertyFile file="${config.dir}/patches_todeploy_${destination}.xml">
  <XMLtag tagname="patch">
    <XMLattribute name="patch.number" value="${new.patch.number}" />
    <XMLattribute name="patch.name" value="${new.patch.name}" />
    <XMLattribute name="patch.description" value="${new.patch.description}" />
  </XMLtag>
  <XMLtag tagname="patches">
    <XMLattribute name="quantity" type="int" operation="+" default="1" />
  </XMLtag>
</XMLPropertyFile>

giving the following XML (ignoring headers for now :)):

<patch patch.number="1" patch.name="p20020813_r2_v2_p1" patch.description="bla 
bla bla bla bla" />
<patch patch.number="2" patch.name="p20020924_r2_v2_p1" patch.description="bla 
bla bla bla bla" />
<patch patch.number="3" patch.name="p20020924_r2_v2_p2" patch.description="bla 
bla bla bla bla" />
<patches quantity="3" />

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message