Re: advanced property configuration
Nicola Ken Barozzi <[email protected]>
| Newsgroups | gmane.comp.krysalis.devel |
|---|---|
| Message-ID | <[email protected]> |
[email protected] wrote: >>Nicola Ken Barozzi wrote: >> >>Michael Homeijer wrote: >> >> > I am going to use centipede (or is it going to be AntWorks? or ..) for a >> > company build environment. >> > To support deployment and compilation of an application for development, >> > test, acceptance testing, production we need more advanced property >> > configuration than the XmlProperty task. >> >> There is another task that makes it possible to read a property file and >> getting valies via xpath, that is much more powerful. What is the extra >> part that you need? Maybe we can simply patch the xmlproperty task (that >> BTW originated here with Centipede). > > Is the task you are talking about available, or is it the 'embed' proposal the is referred > to at the wiki? The embed proposal. > Because I couldn't find the jxpath: property implementation I have implemented a > workaround. In the init antlet, I have translated the module.xml to an ant build that > contains the right properties and their xpath value (see module2properties in the init > antlet). > > This solution would probably even better to use to transform the properties.xml to remove > all nodes that are tagged with the wrong environment attribute or something. Hmmm, clever, but IMHO the embed proposal is much better. > Thnx for the idea. I'll try to come up with a sample. :-) -- Nicola Ken Barozzi [email protected] - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click