Thanks for the contribution!

Would you mind please submitting this as a JIRA issue. Makes it easier to track.
http://issues.apache.org/jira

We're just about to freeze features for Velocity 1.5. If you'd like to get this in there for that version we'll need test cases and doc updates. Otherwise it will be targeted at 1.6. Finally, we'll need to ensure this is 100% backwards compatible (this is a drop-in upgrade) and won't break any existing user setups.

Thanks, WILL

----- Original Message ----- From: "Hilco Wijbenga" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, November 17, 2005 11:45 AM
Subject: [PATCH] TexenTask - Support for <property> and <propertyset>


I needed TexenTask to have support for <property> and <propertyset>
nested elements so that

<texen ...>
 <property name='...' value='...'/>
 <propertyset .../>
</texen>

would put the referenced properties in the context.

This makes using TexenTask much easier.

I've also added some changes to texen.xml to explain the new
functionality. Notably, Ant property names such as 'ns:a.b.c' become
'$ns_a_b_c' in Velocity.

Please let me know if there are any problems with this patch.

Thanks,
Hilco

P.S. I noticed that '$${ns:a.b.c}' generates a parser error (due to the
':'). Noting the double '$', shouldn't this just show up as literal text
in the generated file, i.e. as '${ns:a.b.c}'?


---------------------------------------------------------------------
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]

Reply via email to