An xpath task is something that I've been thinking of for a while but never
got around to writing. I can try having a stab at it again if it helps.
-----Original Message-----
From: Scott Sanders <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: 21 April 2001 23:59
Subject: Re: PATCH -AntGump: antgump-each.xsl
>> btw, we are also in the process of changing how index.html
/cvs_index.html
>> are generated.
>> I find it better to generate an XML from sorted.xml like this:
>> <projects>
>> <project name="foo" status="TAG-foo-STATUS" time="TAG-foo-TIME"
>> cvstime=..../>
>> ...
>> </projects>
>>
>> and replace tags directly in it from antgump_each.xsl . Then a stylesheet
is
>> applied to generate cvs_index.html and index.html. It allows a more
flexible
>> solution and we can add colors like Sam is doing for GUMP (ie red for
fail
>> and yellow for prereq)
>>
>> Does it sounds good to you ?
>
>Yeah, it sounds good. The only thing that I would mention is that
>index.html and cvs_index.html are re-generated after each project run.
>Sam like to see the results as they happen, and so do I.
>
>Does anyone know of any XPath Ant tasks that are available?
>
>I am looking for the ability to update some XPath expression's value.
>In the above example, I would just run something like:
>
> <xpath file="index.xml"
> expr="/projects/project/@status"
> value="SUCCESS"/>
>
>That way we don't have to mess around with the tag naming ;-)
>
>Scott
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
