I'm sorry, I just haven't had time to participate on this version. I hope my
lack of participation doesn't continue. Anyway, thanks for the hard work
Nathan, I know these builds are allot of work.
+0
On Apr 12, 2010, at 21:04 , Nathan Bubna wrote:
> Well, still no update from Will on VELOCIT
Thanks for the work Nathan.
+0
On Apr 17, 2010, at 0:16 , Nathan Bubna wrote:
> Ok, everyone seems happy with the build at this point, so it's time to vote:
>
> The build is still available here:
> http://people.apache.org/~nbubna/velocity/tools/2.0/
>
> Please vote regarding your support for
For what it is worth, mines a +0
On Dec 14, 2009, at 11:23 , Nathan Bubna wrote:
The vote has passed, i'll try to get this ready for a Wednesday
announcement.
+1 from
Claude Brisson
Henning Schmiedehausen
Nathan Bubna
Malcolm Edgar
Adrian A.
--
[
https://issues.apache.org/jira/browse/VELOCITY-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773349#action_12773349
]
Byron Foster commented on VELOCITY-715:
---
The WeakHashMap will correctly drop
[
https://issues.apache.org/jira/browse/VELOCITY-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772172#action_12772172
]
Byron Foster commented on VELOCITY-739:
---
My preference would be the cur
[
https://issues.apache.org/jira/browse/VELOCITY-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745446#action_12745446
]
Byron Foster commented on VELOCITY-731:
---
There was a discussion about thi
On Jul 13, 2009, at 11:44 , tl56 wrote:
Hello
I am new to velocity so please excuse me if this is a foolish
question, but
I have a foreach loop and I'd like to display the data within an excel
sheet(exporting data to excel)like the following
20 20 40 50 instead of
20
20
40
50.
My code:
#forea
ects Versions: 1.6.1
Reporter: Byron Foster
Priority: Minor
The following VTL:
$.x
renders as:
.x
Which eats the dollar sign.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment
[
https://issues.apache.org/jira/browse/VELOCITY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712548#action_12712548
]
Byron Foster commented on VELOCITY-718:
---
I tried to reproduce, but didn't
[
https://issues.apache.org/jira/browse/VELOCITY-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709126#action_12709126
]
Byron Foster commented on VELOCITY-659:
---
I wonder why Gump has only rece
[
https://issues.apache.org/jira/browse/VELOCITY-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12687997#action_12687997
]
Byron Foster commented on VELOCITY-496:
---
I wonder if VELOCITY-406 is good en
[
https://issues.apache.org/jira/browse/VELOCITY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12687992#action_12687992
]
Byron Foster commented on VELOCITY-696:
---
Yea, I should have closed this issue
On Mar 12, 2009, at 18:18 , Nathan Bubna wrote:
In 1.x we have:
directive.set.null.allowed = false
I think that we should flip that to true and perhaps even remove the
option in 2.0.
Agreed.
-
To unsubscribe, e-mail: dev-u
[
https://issues.apache.org/jira/browse/VELOCITY-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681456#action_12681456
]
Byron Foster commented on VELOCITY-698:
---
yea, no need for this anymore.
[
https://issues.apache.org/jira/browse/VELOCITY-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster closed VELOCITY-695.
-
Resolution: Fixed
Better huu? :) Ok, looks like this is going in, so I'll close it. C
[
https://issues.apache.org/jira/browse/VELOCITY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681451#action_12681451
]
Byron Foster commented on VELOCITY-697:
---
Sounds good, I was leaving it open
What OS is this? If you are using the 'cp' command on the command
line with Linux then try 'mv' instead.
On Mar 9, 2009, at 16:24 , Jessica Mong wrote:
I will raise a new Jira issue after some investigation. I will put
some
error messages inside FileResourceLoader and spring
VelocityView.
[
https://issues.apache.org/jira/browse/VELOCITY-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679813#action_12679813
]
Byron Foster commented on VELOCITY-711:
---
I've played with dynamic sco
[
https://issues.apache.org/jira/browse/VELOCITY-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster closed VELOCITY-711.
-
Resolution: Invalid
> Add a #scope directive for modifying scope behav
[
https://issues.apache.org/jira/browse/VELOCITY-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679491#action_12679491
]
Byron Foster commented on VELOCITY-711:
---
Hmm, true, I was thinking the sco
[
https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679027#action_12679027
]
Byron Foster commented on VELOCITY-704:
---
I like your proposal Nathan, and I
: Engine
Reporter: Byron Foster
Fix For: 1.7
A propose adding a #scope block directive that would take a context as an
argument, and all VTL within the #scope block would be executed using the given
scope. The need for this directive comes up when using block macros
: Velocity
Issue Type: Bug
Components: Engine
Affects Versions: 1.7
Reporter: Byron Foster
With the following property setting
velocimacro.library.autoreload = on
A new macro definition within a velocimacro library is not registered without a
re-initializing
sions: 1.7
Reporter: Byron Foster
Fix For: 1.7
Given the following VTL:
#set($var = "\\" )
#set($var2 = "${var}")
results in the following parse error:
Encountered "${" at test.vm[line 2, column 15]
Was expecting one of:
...
.
[
https://issues.apache.org/jira/browse/VELTOOLS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677908#action_12677908
]
Byron Foster commented on VELTOOLS-115:
---
Looking at this some more. I don&#x
[
https://issues.apache.org/jira/browse/VELOCITY-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677902#action_12677902
]
Byron Foster commented on VELOCITY-705:
---
Yea, the writeReference method was re
[
https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677789#action_12677789
]
Byron Foster commented on VELOCITY-704:
---
You know I think these discussions
[
https://issues.apache.org/jira/browse/VELTOOLS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677738#action_12677738
]
Byron Foster commented on VELTOOLS-115:
---
Thanks for the links. If you don
[
https://issues.apache.org/jira/browse/VELOCITY-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677552#action_12677552
]
Byron Foster commented on VELOCITY-705:
---
There is the notion of the Context e
[
https://issues.apache.org/jira/browse/VELOCITY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677542#action_12677542
]
Byron Foster commented on VELOCITY-706:
---
Agreed, I think it would be pr
[
https://issues.apache.org/jira/browse/VELTOOLS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677541#action_12677541
]
Byron Foster commented on VELTOOLS-115:
---
It seems like the default behavior sh
[
https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677534#action_12677534
]
Byron Foster commented on VELOCITY-704:
---
I think having an independent $eval
[
https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676092#action_12676092
]
Byron Foster commented on VELOCITY-704:
---
On the pro side I think the approac
[
https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675587#action_12675587
]
Byron Foster commented on VELOCITY-704:
---
I'll try it out. What abou
It should be Java 1.4, I fixed the autoboxing in trunk, try again...
On Feb 21, 2009, at 8:32 , Antonio Petrelli wrote:
Hi all
I downloaded the sources of the engine from the trunk (1.7-dev version
I suppose), and I noticed that I have a compile problem in
BlockMacroTestCase.testRecursiveBlock
[
https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675402#action_12675402
]
Byron Foster commented on VELOCITY-704:
---
this is for a 2.0 version? I'm
[
https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675389#action_12675389
]
Byron Foster commented on VELOCITY-704:
---
For instance, #break exists all the
[
https://issues.apache.org/jira/browse/VELOCITY-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675204#action_12675204
]
Byron Foster commented on VELOCITY-695:
---
Fair enough, does the balance change
[
https://issues.apache.org/jira/browse/VELOCITY-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675200#action_12675200
]
Byron Foster commented on VELOCITY-680:
---
That's cool, I can go wi
[
https://issues.apache.org/jira/browse/VELOCITY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675195#action_12675195
]
Byron Foster commented on VELOCITY-704:
---
This is more then what I was thinkin
[
https://issues.apache.org/jira/browse/VELOCITY-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675184#action_12675184
]
Byron Foster commented on VELOCITY-680:
---
How about the suggestion that Claude
+1
Thanks Claude for handling this release, and thanks Nathan for
handling all the bug fixes.
On Feb 19, 2009, at 8:59 , Claude Brisson wrote:
Time to release this build as 1.6.2?
[x] +1 Let's do it
[ ] +0 Have fun; i don't care.
[ ] -0 Not sure about this, but i won't stop you.
[ ] -1 No
[
https://issues.apache.org/jira/browse/VELOCITY-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674796#action_12674796
]
Byron Foster commented on VELOCITY-703:
---
But I don't want to be fre
[
https://issues.apache.org/jira/browse/VELOCITY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674784#action_12674784
]
Byron Foster commented on VELOCITY-696:
---
Syntax styles are difficult bec
[
https://issues.apache.org/jira/browse/VELOCITY-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674771#action_12674771
]
Byron Foster commented on VELOCITY-680:
---
Yea, I've leaned away
On Feb 17, 2009, at 23:19 , Claude Brisson wrote:
On mar, 2009-02-17 at 20:56 -0700, Byron Foster wrote:
I believe firmly in not compromising the simplicity of VTL at the
expense of additional functionality, and I think it's great that non-
programmers can be productive in it. I believe
[
https://issues.apache.org/jira/browse/VELOCITY-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674605#action_12674605
]
Byron Foster commented on VELOCITY-698:
---
'parse' is simply a key
[
https://issues.apache.org/jira/browse/VELOCITY-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster closed VELOCITY-690.
-
Resolution: Fixed
> Do not require block directive to have parenthe
[
https://issues.apache.org/jira/browse/VELOCITY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster closed VELOCITY-699.
-
Resolution: Won't Fix
Fix Version/s: 2.0
> Add a #return directive for returnin
[
https://issues.apache.org/jira/browse/VELOCITY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674464#action_12674464
]
Byron Foster commented on VELOCITY-699:
---
Ok, this is an optional directive
[
https://issues.apache.org/jira/browse/VELOCITY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster closed VELOCITY-700.
-
Resolution: Won't Fix
Fix Version/s: 2.0
Looks like this is a no-go.
> Add
[
https://issues.apache.org/jira/browse/VELOCITY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster resolved VELOCITY-696.
---
Resolution: Fixed
I've moved this functionality into a custom directive called #for
I believe firmly in not compromising the simplicity of VTL at the
expense of additional functionality, and I think it's great that non-
programmers can be productive in it. I believe that all the changes I
have proposed or implemented are consistent with that. However, there
are also sophi
[
https://issues.apache.org/jira/browse/VELOCITY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674440#action_12674440
]
Byron Foster commented on VELOCITY-700:
---
FYI, i'm also still considerin
> --
>
> Key: VELOCITY-699
> URL: https://issues.apache.org/jira/browse/VELOCITY-699
> Project: Velocity
> Issue Type: New Feature
> Components: Engine
>Affects Versi
[
https://issues.apache.org/jira/browse/VELOCITY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674433#action_12674433
]
Byron Foster commented on VELOCITY-699:
---
Hmm, I didn't expect resistanc
[
https://issues.apache.org/jira/browse/VELOCITY-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674412#action_12674412
]
Byron Foster commented on VELOCITY-698:
---
I actually implemented this as #
Affects Versions: 2.0
Reporter: Byron Foster
if the last argument to to the #foreach directive is a word, then that word
serves as a label to indicate the break level for the #break directive. Par
exemple:
#foreach($user in $users outer)
#foreach($email in $user.emails
: Engine
Affects Versions: 2.0
Reporter: Byron Foster
The #return directive would be used to return from a macro call, for example:
#macro(foo)
green
#return
eggs and ham
#end
would render:
green
--
This message is automatically generated by JIRA.
-
You can reply to
[
https://issues.apache.org/jira/browse/VELOCITY-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674256#action_12674256
]
Byron Foster commented on VELOCITY-696:
---
When the 'index' keyword is
[
https://issues.apache.org/jira/browse/VELOCITY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster closed VELOCITY-646.
-
Resolution: Won't Fix
Leaving this as is for better backward compatibility the new #fo
Project: Velocity
Issue Type: New Feature
Components: Engine
Affects Versions: 2.0
Reporter: Byron Foster
#stop(template) will only stop the current template, so if the template is
called with a #parse command, then rendering will end within the given
[
https://issues.apache.org/jira/browse/VELOCITY-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674072#action_12674072
]
Byron Foster commented on VELOCITY-695:
---
You seem to be saying that you don&#x
Reporter: Byron Foster
Add the ability to specify default parameters to macros, for example:
#macro(foo $x $y="legit")$x$y#end
calling this with #foo(2) would give:
2legit
Any number of default parameters can be specified, but no non-default
parameters can not follow default
Anakia for
our site docs, then we should be switching it over to use the
independent Anakia project. I tried to build the docs w/maven real
quick, but Maven seems unable to compile 2.x right now. I'll try to
check on this again later if no one else gets to it.
On Sat, Feb 14, 2009 at 9:48 PM,
Type: Improvement
Components: Engine
Affects Versions: 2.0
Reporter: Byron Foster
Allow the following:
#foreach($user in $users index $i)
#end
So that $i holds the current index number of the iteration. This is similar in
functionality to the implicitly defined index
Versions: 2.0
Reporter: Byron Foster
Add comments for Macro definitions so this type of thing is possible:
#macro(foo## This is a comment about foo
$bar ## This is the bar parameter
## It has man uses
$bar2 ## Another
The missing Anakia task in the 2.0 branch is causing the build to
fail. Is see that it was removed because it was deprecated. Do we
have an alternative way to generate the site docs?
-
To unsubscribe, e-mail: dev-unsubscr..
[
https://issues.apache.org/jira/browse/VELOCITY-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673502#action_12673502
]
Byron Foster commented on VELOCITY-692:
---
To clarify my original comment, ye
[
https://issues.apache.org/jira/browse/VELOCITY-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672521#action_12672521
]
Byron Foster commented on VELOCITY-692:
---
This is probably a good opportunit
[
https://issues.apache.org/jira/browse/VELOCITY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672515#action_12672515
]
Byron Foster commented on VELOCITY-688:
---
Nathan, the answer to your questio
[
https://issues.apache.org/jira/browse/VELOCITY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672312#action_12672312
]
Byron Foster commented on VELOCITY-688:
---
Well, I figure rendering $foo as a b
Yea, a complete failure of a commit. It picked up benchmark changes
which are not a big deal, but didn't pick up the intended changes.
the "0 syntax" is a shell substitution of "$! syntax" :), I meant the
the literal "$!". No gold star for me today...
On Feb 10, 2009, at 7:53 , Nathan B
[
https://issues.apache.org/jira/browse/VELOCITY-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster closed VELOCITY-691.
-
Resolution: Won't Fix
Hmm, looking at this more, There is more change I'd like to do
Components: Engine
Affects Versions: 2.0
Reporter: Byron Foster
Change Context Event handling API so that The Context EventCartridge is
initialized with the global EvenCartridge. Then during rendering only the
Context EventCartridge needs to be checked instead of potentially two
[
https://issues.apache.org/jira/browse/VELOCITY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672158#action_12672158
]
Byron Foster commented on VELOCITY-688:
---
Changed the orientation of this fea
[
https://issues.apache.org/jira/browse/VELOCITY-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671576#action_12671576
]
Byron Foster commented on VELOCITY-690:
---
This change also allows block macro
: Engine
Affects Versions: 2.0
Reporter: Byron Foster
Block directives are currently required by the parser to contain parenthesis,
which includes block macros. So
#...@foo
#end
is not allowed, and neither are custom block directives. Removing this
requirement makes the syntax
[
https://issues.apache.org/jira/browse/VELOCITY-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671567#action_12671567
]
Byron Foster commented on VELOCITY-680:
---
I guess I prefer the brevity of #l
[
https://issues.apache.org/jira/browse/VELOCITY-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671455#action_12671455
]
Byron Foster commented on VELOCITY-680:
---
I've added Nathan's sugges
Hey, what's the process of putting up Alpha and Beta versions on the
Velocity site?
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
On Feb 5, 2009, at 21:45 , Leon sdh5724 wrote:
Dear Devs,
Velocity is a great opensource component for weg page render.
We deploy it on our site that render dynamic web pages more than 1
billion pages everyday.
Wow, 1 Billion... That's traffic.
But velocity have no security protecte
[
https://issues.apache.org/jira/browse/VELOCITY-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671003#action_12671003
]
Byron Foster commented on VELOCITY-680:
---
Oops, hit save too soon...
The s
[
https://issues.apache.org/jira/browse/VELOCITY-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671002#action_12671002
]
Byron Foster commented on VELOCITY-680:
---
I've added both the #global a
[
https://issues.apache.org/jira/browse/VELOCITY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670087#action_12670087
]
Byron Foster commented on VELOCITY-681:
---
I looked at this some more, and my
On Feb 2, 2009, at 12:22 , Claude Brisson wrote:
Rather confusing vote indeed... half of the votes ended up on the
private list, and there was a conditional vote.
I think we should just cc the votes to the private list so that busy
people see it, but dev should stay the main list for votes.
I
[
https://issues.apache.org/jira/browse/VELOCITY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster resolved VELOCITY-688.
---
Resolution: Fixed
> ! preceding a reference in strict mode ignores a null except
: Improvement
Components: Engine
Affects Versions: 1.7
Reporter: Byron Foster
Fix For: 1.7
Change strict mode (runtime.references.strict = true) behavior such that when
Velocity attempts to render a reference that evaluates to null then throw an
exception. If the
[
https://issues.apache.org/jira/browse/VELOCITY-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669004#action_12669004
]
Byron Foster commented on VELOCITY-687:
---
Ok, I would argue the viabilit
[
https://issues.apache.org/jira/browse/VELOCITY-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster updated VELOCITY-687:
--
Affects Version/s: (was: 1.7)
2.0
> Macro pass by value opt
[
https://issues.apache.org/jira/browse/VELOCITY-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667773#action_12667773
]
Byron Foster commented on VELOCITY-687:
---
it will add complexity to internal
[
https://issues.apache.org/jira/browse/VELOCITY-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster updated VELOCITY-687:
--
Attachment: value.patch
> Macro pass by value opt
[
https://issues.apache.org/jira/browse/VELOCITY-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster resolved VELOCITY-669.
---
Resolution: Fixed
> Concurrency bug introduced in 1.7-
[
https://issues.apache.org/jira/browse/VELOCITY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667727#action_12667727
]
Byron Foster commented on VELOCITY-681:
---
I applied this patch locally to 1.6.x
On Jan 27, 2009, at 4:37 , Claude Brisson wrote:
Yet another candidate release for 1.6.2, and this time I directly
attempt a vote...
Sorry to be a PITA, but I don't believe that this issue has been
resolved:
https://issues.apache.org/jira/browse/VELOCITY-681
---
Reporter: Byron Foster
Add a configuration property which would change macro parameter passing from
pass by name, to pass by value. I think in many instances this option will
provide behavior that is more intuitive to the user. There are two important
exceptions to this, references created by
[
https://issues.apache.org/jira/browse/VELOCITY-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667294#action_12667294
]
Byron Foster commented on VELOCITY-669:
---
Unless there is further input I
[
https://issues.apache.org/jira/browse/VELOCITY-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666972#action_12666972
]
Byron Foster commented on VELOCITY-686:
---
Looking at the Define direc
[
https://issues.apache.org/jira/browse/VELOCITY-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byron Foster resolved VELOCITY-673.
---
Resolution: Fixed
This also fixes an initialization race condition when using the default
[
https://issues.apache.org/jira/browse/VELOCITY-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666895#action_12666895
]
Byron Foster commented on VELOCITY-652:
---
With the default settings there i
1 - 100 of 308 matches
Mail list logo
