Re: svn commit: r491783 - in /velocity/engine/trunk/build: build.properties

2007-01-03 Thread Claude Brisson
Le mercredi 03 janvier 2007 à 00:50 +, Henning P. Schmiedehausen a écrit : [EMAIL PROTECTED] writes: Hi, while I'm basically +1 for the patch (lazy consensus), can you please document each of the properties inside build.properties. ATM they seem to be self-explanatory but in six

[jira] Commented: (VELOCITY-149) allow for deeply nested macro calls

2007-01-03 Thread Christoph Reck (JIRA)
[ https://issues.apache.org/jira/browse/VELOCITY-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461924 ] Christoph Reck commented on VELOCITY-149: - The multi-line directives of (upcoming) 1.5 release and the

Re: [jira] Created: (VELOCITY-509) Add new directive #evaluate

2007-01-03 Thread apache
No, the #evaluate directive is to be used as it the following example: #set( $error = $i18n_tool.getMessage(ERROR123) ) #evaluate( $error )## reder by merging with context It something like the #parse directive, but the content comes from a string and not a file. :) Christoph Geir Magnusson

[jira] Commented: (VELOCITY-149) allow for deeply nested macro calls

2007-01-03 Thread Will Glass-Husain (JIRA)
[ https://issues.apache.org/jira/browse/VELOCITY-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461957 ] Will Glass-Husain commented on VELOCITY-149: Is the Macro with Body Content idea (from the email) in

Re: [RESULT] [VOTE] Release VelocityTools 1.3-beta1

2007-01-03 Thread Nathan Bubna
Hmm. I didn't notice the beta directory. Yeah, i can move 1.3-beta1, but i don't approve of the distinction. Alphas and betas are releases. If we vote on it and announce it (as i will as soon as i can get my feet under myself after the holidays and update all the download links), then it is a

Re: #evaluate

2007-01-03 Thread Nathan Bubna
The more canonical example for an evaluate tool (or directive) is being ably to dynamically decide what method to call on a particular reference. So, something along the lines of: #if( $this $that ) #set( $method = $foo ) #else #set( $method = $bar ) #end $render.eval( \${someRef}.${method}

1.5 Release Timeline

2007-01-03 Thread Malcolm Edgar
Hi All, I know its the perennial question, but do you have a feeling for the release date for Velocity 1.5, am working up to a minor Click release and want to know if I should have it follow the Velocity 1.5 release. regards Malcolm Edgar

Re: 1.5 Release Timeline

2007-01-03 Thread Will Glass-Husain
I'm not sure a beta3 will be necessary unless there are further delays. Looking at JIRA, all replicatable bugs have been resolved and all issues with patches (save 1) have been added. We should go straight for rc1. And yes, I'd be glad to be spokesperson for press inquiries. Henning and I