Dominique Devienne wrote:
On Wed, May 20, 2009 at 2:28 PM, Dave Pawson wrote:
2009/5/20 Dominique Devienne :
Yes, that's what I generate. Except I run through the properties file
and the build file to ensure I get all the (used) properties!
As apposed to what I remembered to put in (and didn't
2009/5/21 Dominique Devienne :
>> An example please Dominique?
>
> XML elements reading properties without the ${name} notation
>
>
>
> ...
>
> XML elements writing properties affecting the rest of the build:
>
>
>
I've not seen any of those.
Perhaps you could provide me with an example bui
On Wed, May 20, 2009 at 11:25 PM, Dave Pawson wrote:
> 2009/5/20 Dominique Devienne :
>
>> I suggested postprocessing Ant's output as there are can hidden use of
>> properties which is not easy to pick up by parsing the Ant XML file
>> (they don't look like ${name} in attributes for example), and
2009/5/20 Dominique Devienne :
> I suggested postprocessing Ant's output as there are can hidden use of
> properties which is not easy to pick up by parsing the Ant XML file
> (they don't look like ${name} in attributes for example), and could
> thus possibly pick up info on more properties.
An
On Wed, May 20, 2009 at 3:24 PM, Dave Pawson wrote:
> 2009/5/20 Dominique Devienne :
>
>> Maybe running in verbose or debug mode and grepping for all property
>> related messages, especially those about not finding the property, and
>> convert that into a build similarly to what you did? --DD
>
>
2009/5/20 Dominique Devienne :
> Maybe running in verbose or debug mode and grepping for all property
> related messages, especially those about not finding the property, and
> convert that into a build similarly to what you did? --DD
Yes
Possibly.
I chose Python and xslt.
I gather you don't fin
On Wed, May 20, 2009 at 2:28 PM, Dave Pawson wrote:
> 2009/5/20 Dominique Devienne :
> Yes, that's what I generate. Except I run through the properties file
> and the build file to ensure I get all the (used) properties!
> As apposed to what I remembered to put in (and didn't change).
> That's th
2009/5/20 Dominique Devienne :
> On Wed, May 20, 2009 at 1:38 PM, Dave Pawson wrote:
>> I keep changing them which results in undefined variables which ant
>> ignores, spreading odd filenames all over the place.
>
> What I used to do was use with a nested condition asserting for
> some properties
On Wed, May 20, 2009 at 1:38 PM, Dave Pawson wrote:
> I keep changing them which results in undefined variables which ant
> ignores, spreading odd filenames all over the place.
What I used to do was use with a nested condition asserting for
some properties to be defined were indeed defined. Abor
I've been writing a couple of ant build files in which I've defined
quite a few variables in an included properties file.
A couple of variables within the build.xml too.
I keep changing them which results in undefined variables which ant
ignores, spreading odd filenames all over the place.
I've s
10 matches
Mail list logo
