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 atte
Good point. if we did this, keeping it simple (with the default
context) makes a lot of sense.
The #evaluate functionality seems simple enough, I'm enthused about
including it (eventually, anyway).
WILL
On 1/3/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
The more canonical example for an "eva
[
https://issues.apache.org/jira/browse/VELOCITY-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen resolved VELOCITY-504.
-
Resolution: Won't Fix
Well, there is not much that I can add. Your anal
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
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}.${metho
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
That makes sense. Maps, anything implementing get/put, and Context objects.
WILL
On 1/3/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
On Jan 3, 2007, at 9:23 AM, Will Glass-Husain wrote:
> [I'm changing the subject line-- I kept looking for this discussion
> in JIRA]
>
> Great way of way
On Jan 3, 2007, at 9:23 AM, Will Glass-Husain wrote:
[I'm changing the subject line-- I kept looking for this discussion
in JIRA]
Great way of way of framing this, Christopher. Thinking about
#evaluate as a companion to #include and #parse makes me realize this
new proposed directive fits w
[I'm changing the subject line-- I kept looking for this discussion in JIRA]
Great way of way of framing this, Christopher. Thinking about
#evaluate as a companion to #include and #parse makes me realize this
new proposed directive fits within the Velocity approach.
Another idea is to have an o
[
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
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 J
Do you mean
$foo = "#foreach($a in $b) .. #end"
?
If so, why not just do it that way, rather than add a new directive?
geir
On Jan 2, 2007, at 11:47 PM, Will Glass-Husain (JIRA) wrote:
Add new directive #evaluate
---
Key: VELOCITY-509
[
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 bett
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
14 matches
Mail list logo
