[
https://issues.apache.org/jira/browse/VELOCITY-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-525.
---
Resolution: Fixed
I did some style "cleanup", but really i don't see wha
[
https://issues.apache.org/jira/browse/VELOCITY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-631:
--
Priority: Minor (was: Major)
Fix Version/s: 1.6
Would be nice to fix this for 1.6
[
https://issues.apache.org/jira/browse/VELOCITY-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-629.
---
Resolution: Fixed
Fix Version/s: 1.6
> Error message for set directive repo
[
https://issues.apache.org/jira/browse/VELOCITY-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-630.
---
Resolution: Fixed
Fix Version/s: 1.6
Fixed in revision 705288.
> Pass by n
[
https://issues.apache.org/jira/browse/VELOCITY-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640218#action_12640218
]
Nathan Bubna commented on VELOCITY-630:
---
In this the "Strange pas
STs
> would not be necessary.
>
> While I'm rambling... I would also make macros local scope, and create a
> global directive. Pass by name would work with local scope, which is
> currently not the case. I think all of this would lead to more intuitive
> behavior that coul
Object value = i.next();
-context.localPut(elementKey, value);
+put(context, elementKey, value);
On Tue, Oct 14, 2008 at 9:40 PM, Nathan Bubna <[EMAIL PROTECTED]> wrote:
> hmm. i suppose that makes sense... of course, i'm too tired to think
> straight
hmm. i suppose that makes sense... of course, i'm too tired to think
straight right now. let me re-examine this tomorrow.
On Tue, Oct 14, 2008 at 6:39 PM, Byron Foster <[EMAIL PROTECTED]> wrote:
> So I looked into this some more and here is the deal. This bug was
> introduced with VELOCITY-285.
[
https://issues.apache.org/jira/browse/VELOCITY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639613#action_12639613
]
Nathan Bubna commented on VELOCITY-631:
---
I'm messing around with this o
[
https://issues.apache.org/jira/browse/VELOCITY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-631:
--
Attachment: Velocity631TestCase.java
Here's a test case with an even simpler templa
[
https://issues.apache.org/jira/browse/VELOCITY-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-629:
--
Attachment: Velocity629TestCase.java
Unfortunately, the patch doesn't account for multi
On Sun, Oct 12, 2008 at 8:31 PM, Byron Foster <[EMAIL PROTECTED]> wrote:
> From my perusal the way the macro implementation works is that all
> parameters passed to a macros are AST, even if they are in quotes. This is
> consistent with pass by name. And anyway, if the string was evaluated
> befo
to my knowledge, macro arguments have always been passed by name, even
string literal ones. still, this is an odd case, using the foreach
index reference in a string literal passed to a macro that includes
the foreach which defines that reference. yeah, that's a bug, but my,
what a tangled web it
[
https://issues.apache.org/jira/browse/VELOCITY-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-630:
--
Attachment: Velocity630TestCase.java
Don't have much time to go after this today. Her
[
https://issues.apache.org/jira/browse/VELOCITY-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639179#action_12639179
]
Nathan Bubna commented on VELOCITY-629:
---
Hmm. It's not #set that'
[
https://issues.apache.org/jira/browse/VELOCITY-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-628.
---
Resolution: Fixed
Fix Version/s: 1.6
> No template information in set direct
[
https://issues.apache.org/jira/browse/VELOCITY-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-627.
---
Resolution: Fixed
Fix Version/s: 1.6
thanks, Byron!
> #foreach exception repo
[
https://issues.apache.org/jira/browse/VELOCITY-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-626.
---
Resolution: Fixed
Fix Version/s: 1.6
> Log to error macro excepti
Adrian Tarau has fixed this in the trunk. It will be correct in the
next release.
On Mon, Oct 13, 2008 at 8:12 AM, Serge Knystautas <[EMAIL PROTECTED]> wrote:
> The links on the change report for the latest release are linking to
> the wrong URLs in JIRA. Specifically on
>
> http://velocity.apac
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-618.
---
Resolution: Fixed
> Strict property and method referen
[
https://issues.apache.org/jira/browse/VELOCITY-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-625.
---
Resolution: Fixed
Fix Version/s: 1.6
> Macro generates array bounds except
[
https://issues.apache.org/jira/browse/VELTOOLS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELTOOLS-94.
--
Resolution: Fixed
Fix Version/s: 2.0
I think all of these things are pretty much taken
[
https://issues.apache.org/jira/browse/VELTOOLS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELTOOLS-106:
--
Fix Version/s: 2.x
Affects Version/s: (was: 2.x)
2.0
[
https://issues.apache.org/jira/browse/VELTOOLS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELTOOLS-93:
-
Fix Version/s: 2.0
> Missing infos on tools creat
[
https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-617:
--
Fix Version/s: 1.6
> Jakarta Commons ORO at runt
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-618:
--
Fix Version/s: (was: 1.3.1)
> Strict property and method referen
[
https://issues.apache.org/jira/browse/VELOCITY-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-622.
---
Resolution: Fixed
Fix Version/s: 1.6
> Display consistent file and line num
[
https://issues.apache.org/jira/browse/VELOCITY-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-624.
---
Resolution: Fixed
Fix Version/s: 1.6
> LogChute's only set log level if s
[
https://issues.apache.org/jira/browse/VELOCITY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638467#action_12638467
]
Nathan Bubna commented on VELOCITY-623:
---
Is there any particular reason
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638466#action_12638466
]
Nathan Bubna commented on VELOCITY-618:
---
Yeah, i know very well how bad i
that makes sense to me.
On Thu, Oct 9, 2008 at 3:37 PM, Byron Foster <[EMAIL PROTECTED]> wrote:
> I noticed in the JdkLogChute and Log4jLogChute that if the default logging
> level is set to WARNING. It seems like the log level should be set
> explicity only in the case that the coresponding prop
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638176#action_12638176
]
Nathan Bubna commented on VELOCITY-618:
---
I wouldn't bet against you on d
i'll cast my vote for a third party... :)
3) "/foo.vm[line aa, column bb]
On Wed, Oct 8, 2008 at 6:02 PM, Byron Foster <[EMAIL PROTECTED]> wrote:
> I'd like to submit a patch that changes all the file names and line number
> reported in exception to a consistent format. Currently its difficult
[
https://issues.apache.org/jira/browse/VELOCITY-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637544#action_12637544
]
Nathan Bubna commented on VELOCITY-621:
---
This error has been fixed since 1.6-b
On Mon, Oct 6, 2008 at 10:02 PM, Byron Foster <[EMAIL PROTECTED]> wrote:
>
>
> Nathan Bubna wrote:
>>
>> On Wed, Oct 1, 2008 at 10:40 AM, Byron Foster <[EMAIL PROTECTED]> wrote:
>>>
>>> I was considering the possibility that references within
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637246#action_12637246
]
Nathan Bubna commented on VELOCITY-618:
---
Thanks. the RuntimeMacro change l
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637206#action_12637206
]
Nathan Bubna commented on VELOCITY-618:
---
Could you run that last patch against
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637160#action_12637160
]
Nathan Bubna commented on VELOCITY-618:
---
Byron, this looks great. The only ch
[
https://issues.apache.org/jira/browse/VELOCITY-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-596.
---
Resolution: Fixed
thanks, Adrian!
> Changes report JIRA links don
[
https://issues.apache.org/jira/browse/VELOCITY-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636464#action_12636464
]
Nathan Bubna commented on VELOCITY-619:
---
Not being able to use #if like tha
[
https://issues.apache.org/jira/browse/VELOCITY-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-620:
--
Attachment: (was: Velocity620TestCase.java)
> Parse error creates an obscure er
[
https://issues.apache.org/jira/browse/VELOCITY-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-620:
--
Attachment: Velocity620TestCase.java
latest version of the test...
> Parse error creates
On Thu, Oct 2, 2008 at 3:32 AM, Byron Foster <[EMAIL PROTECTED]> wrote:
> I need a sanity check. I tested this with an unmodified checkout from svn:
>
> URL: http://svn.apache.org/repos/asf/velocity/engine/trunk
> Last Changed Author: nbubna
> Last Changed Rev: 700847
> Last Changed Date: 2008-10-
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-618:
--
Fix Version/s: 1.6
1.5.1
> Strict property and method referen
[
https://issues.apache.org/jira/browse/VELOCITY-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636223#action_12636223
]
Nathan Bubna commented on VELOCITY-596:
---
Hey, do any of you Maven mavens
[
https://issues.apache.org/jira/browse/VELOCITY-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-596:
--
Priority: Minor (was: Major)
Fix Version/s: 1.6
> Changes report JIRA links do
[
https://issues.apache.org/jira/browse/VELOCITY-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-316.
---
Resolution: Fixed
Fix Version/s: (was: 2.0)
1.5
This is
[
https://issues.apache.org/jira/browse/VELOCITY-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636216#action_12636216
]
Nathan Bubna commented on VELOCITY-619:
---
I have mixed feelings about this.
F
[
https://issues.apache.org/jira/browse/VELOCITY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636208#action_12636208
]
Nathan Bubna commented on VELOCITY-618:
---
at first glance, i see two problems:
[
https://issues.apache.org/jira/browse/VELOCITY-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-620:
--
Attachment: (was: Velocity620TestCase.java)
> Parse error creates an obscure er
[
https://issues.apache.org/jira/browse/VELOCITY-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-620:
--
Attachment: Velocity620TestCase.java
> Parse error creates an obscure error mess
[
https://issues.apache.org/jira/browse/VELOCITY-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-620:
--
Attachment: Velocity620TestCase.java
For the first of your examples, 1.6-dev (with the
[
https://issues.apache.org/jira/browse/VELOCITY-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-620.
---
Resolution: Cannot Reproduce
Fix Version/s: 1.6
> Parse error creates an obsc
[
https://issues.apache.org/jira/browse/VELOCITY-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636154#action_12636154
]
Nathan Bubna commented on VELOCITY-337:
---
no, both of your examples are valid
On Wed, Oct 1, 2008 at 10:40 AM, Byron Foster <[EMAIL PROTECTED]> wrote:
> I was considering the possibility that references within macros could be
> optimized. Given the following:
>
> #macro(foo $a $b)
> $a $b
> #end
>
> #foo($c $d.e)
>
> Currently both $a $b within the macro are referenced by A
[
https://issues.apache.org/jira/browse/VELOCITY-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636107#action_12636107
]
Nathan Bubna commented on VELOCITY-554:
---
That's a great patch, Adri
Oops, just saw that you did. Thanks!
On Mon, Sep 29, 2008 at 7:13 AM, Nathan Bubna <[EMAIL PROTECTED]> wrote:
> We actually won't even get your patch otherwise. The mailing list
> strips most attachments off. Please attach this to a JIRA issue. :)
>
> On Mon, Sep 29,
We actually won't even get your patch otherwise. The mailing list
strips most attachments off. Please attach this to a JIRA issue. :)
On Mon, Sep 29, 2008 at 6:58 AM, Claude Brisson <[EMAIL PROTECTED]> wrote:
> Thanks, but you should create an entry in JIRA:
> https://issues.apache.org/jira/brow
[
https://issues.apache.org/jira/browse/VELOCITY-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635194#action_12635194
]
Nathan Bubna commented on VELOCITY-554:
---
yes, 1.7 is great.
> Velocity
[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634618#action_12634618
]
Nathan Bubna commented on VELOCITY-613:
---
Yeah, a 1.5.1 is probably the proper
[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634584#action_12634584
]
Nathan Bubna commented on VELOCITY-613:
---
Fixed the permissions; thanks
[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634555#action_12634555
]
Nathan Bubna commented on VELOCITY-613:
---
I signed the relocation pom and move
[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634554#action_12634554
]
Nathan Bubna commented on VELOCITY-613:
---
Ok, that's a start, but i don&#
[
https://issues.apache.org/jira/browse/VELOCITY-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634544#action_12634544
]
Nathan Bubna commented on VELOCITY-554:
---
Well, that's Henning's con
[
https://issues.apache.org/jira/browse/VELOCITY-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-608.
---
Resolution: Fixed
> Maven build for velocity-site fails because of missing plexus ut
[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634328#action_12634328
]
Nathan Bubna commented on VELOCITY-613:
---
Adrian, would you be willing/able to
update the state of things. note that the only open bug (excluding
improvements and new features) against the code itself (excluding docs
and build stuff) is VELOCITY-615, which has not yet been confirmed to
still exist in 1.6. not too shabby.
On Tue, Sep 23, 2008 at 2:28 PM, Nathan Bubna
[
https://issues.apache.org/jira/browse/VELOCITY-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-337:
--
Assignee: (was: Velocity-Dev List)
Issue Type: Improvement (was: Bug)
> N
[
https://issues.apache.org/jira/browse/VELOCITY-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-340:
--
Issue Type: Improvement (was: Bug)
keeping deprecated stuff around is not a bug. getting
[
https://issues.apache.org/jira/browse/VELOCITY-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-554:
--
Issue Type: New Feature (was: Bug)
this would technically be a new feature. does anyone
[
https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-613.
---
Resolution: Won't Fix
I think this is something better fixed by the maven folks,
[
https://issues.apache.org/jira/browse/VELOCITY-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-609.
---
Resolution: Fixed
Fix Version/s: 1.6
fixed this in the site.xml file the other day
[
https://issues.apache.org/jira/browse/VELOCITY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-567.
---
Resolution: Won't Fix
This is a bug in commons-collections. It wouldn't be appr
[
https://issues.apache.org/jira/browse/VELOCITY-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-587.
---
Resolution: Fixed
> Backslashes throw lexical errors in double-quoted stri
[
https://issues.apache.org/jira/browse/VELOCITY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-616.
---
Resolution: Fixed
> Escaping of directives does not work if the directive is in cu
[
https://issues.apache.org/jira/browse/VELOCITY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-616:
--
Priority: Minor (was: Major)
Fix Version/s: 1.6
Not major, as this feature was new
[
https://issues.apache.org/jira/browse/VELOCITY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-616:
--
Attachment: Velocity616TestCase.java
Test case showing this happens with both the built-in
[
https://issues.apache.org/jira/browse/VELOCITY-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634002#action_12634002
]
Nathan Bubna commented on VELOCITY-466:
---
We use the pom as our pom, but th
[
https://issues.apache.org/jira/browse/VELOCITY-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633997#action_12633997
]
Nathan Bubna commented on VELOCITY-466:
---
My understanding is that this woul
Below is the list of outstanding issues targeted for Velocity 1.6 and
my take on their priority. As you'll notice, i think there are only a
few more that really ought to have some attention before we do a final
1. 6 release. Most of these are things that i'm currently clueless
about or are in cod
The Velocity developers are very pleased to make the first beta
release of Velocity Engine 1.6-beta1 available for download.
This release contains many bugfixes, new features and drastic
performance improvements. Please see the change log
(http://velocity.apache.org/engine/devel/changes-report.htm
8M/66M
> [INFO]
>
> bash-3.00$
>
> works for me. What errors exactly do you get? Maybe I have some env
> variables set differently from you.
>
> I could sudo to your account if you don't
42 AM, Nathan Bubna <[EMAIL PROTECTED]> wrote:
> Ok, in a fit of procrastinating what i should really work on this
> morning, i thought i'd try and do a quick update of the site to show
> the Tools 2.0-beta1 release, and thus ensure i can update the site on
> my new laptop, prior t
[
https://issues.apache.org/jira/browse/VELOCITY-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633541#action_12633541
]
Nathan Bubna commented on VELOCITY-614:
---
Christopher, you've never b
[
https://issues.apache.org/jira/browse/VELOCITY-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633377#action_12633377
]
Nathan Bubna commented on VELOCITY-614:
---
It's not #something($foo) th
[
https://issues.apache.org/jira/browse/VELOCITY-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-614.
---
Resolution: Fixed
Fix Version/s: 1.6
Fixed. But if #something turns out to truly
The vote has passed and the test build will be released as Velocity
Engine 1.6-beta1.
+1 votes from:
Nathan Bubna
Henning Schmiedehausen
matthijs lambooy
Malcolm Edgar
Erron Austin
Claude Brisson
Will Glass-Husain
No other votes.
i'll push this to the mirrors promptly. announcement will
On Fri, Sep 19, 2008 at 9:37 AM, Nathan Bubna <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 19, 2008 at 12:03 AM, Will Glass-Husain
> <[EMAIL PROTECTED]> wrote:
>> +1
>>
>> Built with JDK 1.5 / ant 1.7 on WinXP.
>>
>> A question though-- what happene
i'll remedy that for the next release.
it's a bit late for this one; it'll have to be manually handled.
> WILL
>
> On Thu, Sep 18, 2008 at 1:52 PM, Claude Brisson <[EMAIL PROTECTED]> wrote:
>
>> +1 !
>>
>> Le mercredi 10 septembre 2008 à 11:15 -07
[
https://issues.apache.org/jira/browse/VELOCITY-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632362#action_12632362
]
Nathan Bubna commented on VELOCITY-614:
---
This won't be fixable without p
[
https://issues.apache.org/jira/browse/VELOCITY-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632340#action_12632340
]
Nathan Bubna commented on VELOCITY-614:
---
This looks like a result of the
[
https://issues.apache.org/jira/browse/VELOCITY-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-614:
--
Attachment: Velocity614TestCase.java
here's a test case which confirms it:
[junit] [
[
https://issues.apache.org/jira/browse/VELOCITY-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632292#action_12632292
]
Nathan Bubna commented on VELOCITY-615:
---
You can also get a candidate for
On Wed, Sep 17, 2008 at 11:24 PM, <[EMAIL PROTECTED]> wrote:
> Author: nbubna
> Date: Wed Sep 17 23:24:13 2008
> New Revision: 696572
>
> URL: http://svn.apache.org/viewvc?rev=696572&view=rev
> Log:
> refactor to bridge the gap between ToolManager and VelocityView with a new
> ViewToolManager cla
On Tue, Sep 16, 2008 at 1:46 PM, Christopher Schultz
<[EMAIL PROTECTED]> wrote:
> Nathan,
>
> Nathan Bubna wrote:
>> #whatever({ 'foo' : 'bar', "baz" : "bat" })
>
> I didn't realize that this syntax was possible. I'm
+1 from me
On Tue, Sep 16, 2008 at 8:59 AM, Nathan Bubna <[EMAIL PROTECTED]> wrote:
> There was no negative feedback on the 2nd test build (no feedback at all
> actually), so i'm moving on to a vote again.
>
> The test build is still available here:
> http://people.a
te passes, I'll push
this to the mirrors and perhaps begin struggling to update the web site that
afternoon. Of course, recent history indicates that there's really no
telling when i'll actually succeed with that last part and be able to
announce the release.
On Wed, Sep 10, 200
On Mon, Sep 15, 2008 at 2:57 PM, Christopher Schultz
<[EMAIL PROTECTED]> wrote:
> Nathan,
>
> Nathan Bubna wrote:
>> On Mon, Sep 15, 2008 at 8:53 AM, Will Glass-Husain
>> <[EMAIL PROTECTED]> wrote:
>>> Wouldn't it be more appropriate to pass in a map
On Mon, Sep 15, 2008 at 8:53 AM, Will Glass-Husain
<[EMAIL PROTECTED]> wrote:
> Wouldn't it be more appropriate to pass in a map of parameters?
heh. yeah, why don't they do that?
> On Fri, Sep 12, 2008 at 9:04 AM, Christopher Schultz <
> [EMAIL PROTECTED]> wrote:
>
>> All,
>>
>> I was just remin
I don't know offhand of an easy way to make things more JSP/FM-ish,
and honestly, i don't love the tag-type syntax. So i'm pretty
unmotivated there. As for performance, i think they could clean that
up w/o requiring us to implement new features. They would just need
to give up the tag-ish approa
801 - 900 of 1607 matches
Mail list logo
