he asked to go emeritus.
>>
>> I just checked if I had enough karma to do it myself (editing of
>> private/committers/board/committee-info.txt), and it worked.
>>
>> So no worry, Nathan, nothing to do for you :-)
>>
>> Claude
>>
>>
&
+1 GA
On Wed, Nov 16, 2016 at 7:24 AM, Greg Huber wrote:
> Thanks, works great for me.
>
> [x] General Availability (GA)
>
> +1 non binding.
>
>
> On 16 November 2016 at 11:51, Claude Brisson wrote:
>
> > The Velocity Engine 2.0 RC3 test build has been
+1 deprecate and refactor away. this all sounds good.
On Thu, Nov 17, 2016 at 10:32 AM, Sergiu Dumitriu wrote:
> On 11/17/2016 12:58 PM, Claude Brisson wrote:
> > There are several things I'd like to do for the tools before releasing
> > them:
> >
> > 1) deprecate
+1
On Tue, Oct 11, 2016 at 5:11 AM, Claude Brisson wrote:
> Hi.
>
> Before staging the release candidate for velocity-engine, I must first
> release the version 2 of velocity-master.
>
> It only contains a pom.xml with the list of PMCs and devs, and enumerate
> the mailing
On Mon, Dec 5, 2016 at 9:49 AM, Sergiu Dumitriu
wrote:
> I agree with Michael here, this direction is against what "pure"
> Velocity is about. The generic tools shouldn't be allowed to fetch
> random resources off the internet.
>
I'm with Claude here. Making powerful
Wow. Sounds great, Claude!
On Mon, Jan 2, 2017 at 2:49 AM, wrote:
> Author: cbrisson
> Date: Mon Jan 2 10:49:55 2017
> New Revision: 1776916
>
> URL: http://svn.apache.org/viewvc?rev=1776916=rev
> Log:
> [tools] ImportTool and XmlTool reenginering, along with the addition
On Wed, Jan 4, 2017 at 7:57 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> All,
>
> I'm going to be in Miami for this year's ApacheCon. In all the years
> I've been going to ApacheCons, I've never seen a single presentation on
> Velocity. That probably has something to do with
On Sat, Aug 12, 2017 at 8:50 AM, Michael Osipov wrote:
> Am 2017-08-09 um 12:52 schrieb Claude Brisson:
>
>> The Apache Velocity community is pleased to announce the release of
>> Apache Velocity Engine 2.0. The release is available for download at:
>>
>>
[+1] GA
On Fri, Jul 28, 2017 at 4:00 PM, Claude Brisson wrote:
> The Velocity Engine 2.0 RC9 is available.
>
> Main change since the RC8 is a full review of the DataSourceResourceLoader.
>
> Release notes:
>
> * https://dist.apache.org/repos/dist/dev/velocity/velocity-eng
>
It's here:
http://repo1.maven.org/maven2/org/apache/velocity/velocity-engine-core/2.0/
But we should probably mention the new maven path in the upgrading docs.
On Tue, Aug 8, 2017 at 12:52 PM, Alex Fedotov wrote:
> Maven repo does not seem to show 2.0 for the overall velocity
The links all look good to me, nor can i think of anything missing at this
point.
On Sun, Aug 6, 2017 at 11:01 AM, Claude Brisson wrote:
> The maven artefact has been publish, the release is visible on apache
> mirrors, and the website now shows engine 2.0 documentation.
>
>
On Mon, May 1, 2017 at 9:50 AM, Claude Brisson wrote:
> [ ] Leave at test build
> [ ] Alpha
> [ ] Beta
> [X ] General Availability (GA)
>
Good idea. I'll see what i can do.
On Fri, Dec 8, 2017 at 5:54 AM, Claude Brisson
wrote:
> I don't have enough karma, but we should hear from Nathan.
>
> Also, I wouldn't mind being a JIRA admin on those projects...
>
> Claude
>
>
>
> On 08/12/2017 14:03, Michael
Claude i think you should have the karma, if i'm reading things right; you
were already in the Administrators role. Michael, you are now too.
If i'm wrong, do let me know. We'll figure it out.
On Fri, Dec 8, 2017 at 6:52 AM, Nathan Bubna <nbu...@gmail.com> wrote:
> Good idea. I'll s
On Fri, Dec 8, 2017 at 2:54 PM, Michael Osipov wrote:
> Hi folks,
>
> I have noticed that good bunch of Velocity 0 tickets have been rejected
> though fix version has been set. This is confusing for me and likely
> others. Any reasoning behind this? Fix version implies that
I think i did add you to VELOCITY also. I'll double check.
On Fri, Dec 8, 2017 at 12:21 PM, Michael Osipov <micha...@apache.org> wrote:
> Am 2017-12-08 um 16:00 schrieb Nathan Bubna:
>
>> Claude i think you should have the karma, if i'm reading things right; y
Ah, seems there's two of you in JIRA (or at least two guys w/your name).
I'd only put the [wrong] one. :)
On Fri, Dec 8, 2017 at 12:27 PM, Nathan Bubna <nbu...@gmail.com> wrote:
> I think i did add you to VELOCITY also. I'll double check.
>
> On Fri, Dec 8, 2017 at 12:21 PM,
; BTW the SecurityManager is initialized at startup so one can easily
> > initialize a static boolean in e.g. Velocity.java or whatever and just
> > consult that rather than calling System.getSecurityManager() all the tim
> > e.
> >
> >> I don't really understand e
If you have some good pointers or suggestions...
>>
>> I don't really understand either why we're speaking of the CWD whereas
>> all the VelocityView knows is the webapp root. But I may have missed
>> something.
>>
>>
>> Claude
>>
>> On 21/03/2018
If we're talking 2.x, then adding a PrivilegedAction sounds better. If 3.0
(which, i think needs to happen anyway, right Claude?), then i'd agree with
Michael. The auto config would be better off as something users need to
explicitly turn on, not the default any longer.
On Wed, Mar 21, 2018 at
Thanks to both of you!
On Tue, Oct 2, 2018 at 12:54 PM Michael Osipov wrote:
> Am 2018-10-01 um 22:35 schrieb Claude Brisson:
> > The test build of Velocity Tools 3.0 is available.
> >
> > No determination as to the quality ('alpha,' 'beta,' or 'GA') of
> > Velocity Tools 3.0 has been made, and
On Thu, Oct 4, 2018 at 8:43 AM Claude Brisson
wrote:
> The Velocity Tools 3.0 test build has been available since October 1st.
>
> Release notes:
>
> *
>
> https://dist.apache.org/repos/dist/dev/velocity/velocity-tools/3.0/release-notes.html
>
> Distribution:
>
> *
+1
On Sat, Sep 22, 2018 at 3:58 PM Michael Osipov wrote:
> Hi,
>
> * reformatted the POM to a readible state
> * Apache Parent upgraded to 21
> * added plugin management section for commonly used plugins
>
> Staging repo:
>
g obvious. What exactly is this?
> There doesn't seem to be anything here except a POM file. Is this a
> released product or other artifact?
>
> Thanks, WILL
>
> On Sat, Sep 22, 2018 at 8:23 PM Nathan Bubna wrote:
>
> > +1
> >
> > On Sat, Sep 22, 2018 at
Seems good. No objections here. :)
On Wed, Mar 6, 2019 at 4:23 PM Claude Brisson
wrote:
> 2.1 RC1 is history, 2.1 RC2 is on its way.
>
> Here is a proposal for the configuration keys refactoring:
>
>
> https://velocity.apache.org/engine/devel/configuration-property-changes-in-2.1.html
>
>
+1 Java 8 has been around plenty long
On Fri, Feb 22, 2019 at 3:40 PM Claude Brisson
wrote:
> Hi all.
>
> The VELOCITY-892 branch contains a fix for the corresponding issue [1].
>
> The purpose is to let the method arguments conversion handler manipulate
> the formal arguments types as
Hmm. I may not be the best to weigh in on this, as i never used event
handlers for escaping. I always preferred the direct, explicit control of
escaping via tools, and trusted myself (YMMV) not to forget escaping
anywhere important.
I'll definitely agree that we shouldn't shade. I'm perfectly
[+1] GA
On Tue, Mar 19, 2019 at 5:43 PM Claude Brisson
wrote:
> The Velocity Engine 2.1 RC3 is available since March 15.
>
> Main changes:
>
> * Velocity Engine 2.1 now requires JDK 1.8+
> * Two more backward compatibility flags with 1.7: hyphens in
> identifiers and macros literal
Yeah, adopting Spring support is unlikely to be much burden and seems well
worthwhile.
On Sat, Jun 1, 2019 at 1:48 AM Claude Brisson
wrote:
> Hi.
>
> We are aware of the situation, and we were more or less expecting
> someone to make such a proposal. Yes, it will benefit both communities.
>
>
6
>
> Nathan,
>
> (Apologies for the cross-post, but this is a very dev-y response.
> After this message in the thread, I will reply only on the dev@ list).
>
> On 2/5/20 1:09 PM, Nathan Bubna wrote:
> > Thanks for drilling into that, Chris! I was reading, but have no
> &g
+1 Looks good to me. Thanks, Claude. Hope we can get this out before the
next board report is due. :)
On Wed, Jan 29, 2020 at 5:05 PM Claude Brisson
wrote:
> The test build of Velocity Engine 2.2 RC6 is available.
>
> No determination as to the quality ('alpha,' 'beta,' or 'GA') of
> Velocity
er if just dropping the method is enough: anyone with an old
> format configuration will have trouble identifying the cause of the
> problem. Isn't there any way to tweak beanutils into binding class= to
> setClassname() ?
>
>
>Claude
>
> On 20-02-05 19 h 09, Nathan Bubna wr
Or maybe even just put a 3.x compatible version of the Struts tools up on
github as an independent fork. Probably easier than talking the Struts devs
into it.
On Thu, Feb 6, 2020 at 11:10 PM Claude Brisson
wrote:
> On 20-02-06 16 h 15, Christopher Schultz wrote:
>
> > 3.0 completely dropped
a configuration like it was done
> for other things in 2.1/2.2 ? I have to try :)
>
> On Tue, Jan 14, 2020 at 7:24 PM Nathan Bubna wrote:
> >
> > This is a planned change. Implicit local scope was deprecated in 1.7 for
> > removal in 2.0 and was replaced
2020 at 5:31 PM Nathan Bubna wrote:
> >
> > I don't have any time for dev work on Velocity these days, so it doesn't
> > much matter whether i consider it or not. :) If someone wants to put in
> the
> > work, i won't protest.
>
> > My inclination,
This is a planned change. Implicit local scope was deprecated in 1.7 for
removal in 2.0 and was replaced with explicit scope control objects.
https://velocity.apache.org/engine/devel/upgrading.html#upgrading-from-velocity-16x-to-velocity-17x
On Tue, Jan 14, 2020 at 9:29 AM Thomas Mortagne
wrote:
I'm pretty sure we don't have a setting like that.
On Mon, Dec 14, 2020 at 8:01 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> All,
>
> We recently suffered an OOME in production because we had a huge SQL
> query return a log of data which, in turn, generated even more HTML
>
and
things are pretty stable, so i'm wary of taking on optimizations that
increase our complexity.
On Mon, Dec 14, 2020 at 8:38 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Nathan,
>
> On 12/14/20 11:15, Nathan Bubna wrote:
> > I'm pretty sure we don'
Agreed. Thanks for your long work here, Will. If you're ever in Portland,
drop me a line and i'll buy you a drink. :)
On Thu, Mar 11, 2021 at 12:11 PM Henning Schmiedehausen <
henn...@schmiedehausen.org> wrote:
> Will, Thank you so much for your time and the part of the journey that we
> walked
+1 GA
On Mon, Mar 1, 2021 at 8:06 AM Claude Brisson
wrote:
> The Velocity Engine 2.3 RC1 is available since February 27.
>
> Main changes in this release:
>
> + New spring-velocity-support module, containing Spring framework
> Velocity Engine integration classes.
> + Security fix: let
+1 GA
On Mon, Mar 1, 2021 at 12:26 PM Claude Brisson
wrote:
> The Velocity Tools 3.1 RC1 is available since February 27.
>
> Main changes in this release:
>
> + Added an optional 'factory' attribute to tools with the classname of a
> factory for creating new tools instances
> + Added a new
+1 GA
On Wed, Mar 3, 2021 at 4:29 AM Claude Brisson
wrote:
> The Velocity Engine 2.3 RC2 is available since February 27.
>
> Main changes in this release:
>
> + New spring-velocity-support module, containing Spring framework
> Velocity Engine integration classes.
> + Security fix: let
Thank you, Claude!! I really appreciate all your work getting these
releases out!
On Mon, Mar 8, 2021 at 4:12 PM Claude Brisson wrote:
> The Apache Velocity community is pleased to announce the release of
> Apache Velocity Engine 2.3 The release is available for download at:
>
>
Thank you, Claude! I really appreciate you getting this out.
On Sat, Feb 27, 2021 at 5:14 AM Claude Brisson
wrote:
> The test build of Velocity Engine 2.3 RC1 is available.
>
> No determination as to the quality ('alpha,' 'beta,' or 'GA') of
> Velocity Engine 2.3 RC1 has been made, and at this
+1
On Sat, Feb 27, 2021 at 2:15 AM Claude Brisson
wrote:
> Hi.
>
> Here's an RC for velocity-master-4, with the following changes:
>
> + set maven-enforcer-plugin and extra-enforcer-rules plugins versions
> + removed Antonio as emeritus, as per his request
> + switched scm URLs from svn to git
Henning errantly didn't send this to the list, forwarding it on his behalf.
:)
-- Forwarded message -
From: Henning Schmiedehausen
Date: Sat, Feb 27, 2021 at 8:07 PM
Subject: Re: [VOTE] Release Velocity Master version 4
To: Nathan Bubna
Ok. Thanks.
+1 to release.
On Sat
Agreed. Travis will get over it. :)
On Sat, Feb 27, 2021 at 3:15 AM Claude Brisson
wrote:
> Of course, anticipating upon yet unreleased artifacts breaks CI. But if
> we are to release master, engine and the tools in a raw ASAP to please
> the security team, we should launch parallel release
On Fri, Dec 18, 2020 at 3:01 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Nathan,
>
> On 12/16/20 12:43, Nathan Bubna wrote:
> > In general, i think the overhead from StringWriter is probably pretty
> minimal.
> >
> > Before worrying abou
On Mon, Feb 22, 2021 at 12:13 AM Claude Brisson
wrote:
> From what I understood, it's github which is asking for the change, not
> enforcing it.
>
> For the record, I am supposed to come back to infra with a link to a
> mail thread -aka this one- to act our decision. So +1s needed.
>
> Since
+1
On Sat, Mar 25, 2023 at 4:59 AM Claude Brisson
wrote:
> Hello.
>
> Please vote for the release of the velocity-master release 5.
>
> Changes:
>
> + upgraded parent apache pom to version 29
> + upgraded maven plugins to latest version
> + list Will Glass-Husain as Emeritus (I still wonder why
The javax->jakarta migration is unbelievably wasteful. So much stupid.
But yes, we probably have to make that a major version change. Which is
also very dumb. And unfortunately, i have zero time to help. :(
On Wed, Mar 22, 2023 at 3:24 AM Claude Brisson
wrote:
> And it should be better to
+1
On Sat, Feb 3, 2024 at 10:07 AM Michael Osipov wrote:
> Hi,
>
> Changelog:
> * Upgrade to Apache Parent 31
> * Explicitly require Maven 3.2.5+ at build time
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachevelocity-1040/
>
>
+1
On Sat, Feb 10, 2024 at 11:42 AM Michael Osipov wrote:
> Hi,
>
> IMPORTANT: This requires the following staging repo:
> https://repository.apache.org/content/repositories/orgapachevelocity-1041/
>
> Release notes:
>
>
+1
On Sat, Feb 10, 2024 at 11:33 AM Michael Osipov wrote:
> Hi,
>
> Release notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310104=12352138
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachevelocity-1041/
>
>
Sorry for the late reply. I sadly have very limited time for Apache work
these days.
The commit log is incidental. It would ideally have no repeated versions,
but it's hardly a transgression if it does. Likewise, it's not a
requirement of the ASF that our releases never skip version numbers. It
+1
On Tue, Jul 30, 2024 at 10:34 AM Michael Osipov wrote:
> Hi,
>
> Changelog:
> * Upgrade to Apache Parent 33
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachevelocity-1044/
>
>
[
http://issues.apache.org/jira/browse/VELTOOLS-67?page=comments#action_12449034
]
Nathan Bubna commented on VELTOOLS-67:
--
Looks good. i have a few refinements, but i'll try and get this in on Monday.
As for supporting this with session
[
http://issues.apache.org/jira/browse/VELTOOLS-69?page=comments#action_12450118
]
Nathan Bubna commented on VELTOOLS-69:
--
Hmm. Breaking #if($query.foo) compatibility isn't ok, if we can't find a
reasonable way to keep that and the sub
[ http://issues.apache.org/jira/browse/VELTOOLS-69?page=all ]
Nathan Bubna resolved VELTOOLS-69.
--
Fix Version/s: 1.3
Resolution: Fixed
Ok, the sub is gone as of revision 475480.
ValueParserSub generic getter never worked
[
http://issues.apache.org/jira/browse/VELTOOLS-71?page=comments#action_12451827
]
Nathan Bubna commented on VELTOOLS-71:
--
It's in the changelog now, but i don't think it matters since the building with
jdk 1.3 feature doesn't/didn't work
[
http://issues.apache.org/jira/browse/VELTOOLS-72?page=comments#action_12454119
]
Nathan Bubna commented on VELTOOLS-72:
--
heh. i just realized i made myself a hypocrite by rashly assuming you meant
the commit-then-review comment to say
[ http://issues.apache.org/jira/browse/VELTOOLS-70?page=all ]
Nathan Bubna resolved VELTOOLS-70.
--
Resolution: Fixed
Ok. So far as i can tell, we are fully Struts 1.3.x compatible now. All has
been upgraded.
Upgrade to Struts 1.3.x and update
[ http://issues.apache.org/jira/browse/VELTOOLS-9?page=all ]
Nathan Bubna resolved VELTOOLS-9.
-
Fix Version/s: (was: 1.3)
Resolution: Won't Fix
I don't know how to do this, have interest in it myself, or care to wait any
longer for folks
[
http://issues.apache.org/jira/browse/VELOCITY-502?page=comments#action_12460669
]
Nathan Bubna commented on VELOCITY-502:
---
I don't really care. Both have advantages, both will work fine. If you're
going to do the work, i say you
[
http://issues.apache.org/jira/browse/VELOCITY-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461798
]
Nathan Bubna commented on VELOCITY-504:
---
So, in order to trigger the issue, you have to be using a tool
[
http://issues.apache.org/jira/browse/VELOCITY-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461821
]
Nathan Bubna commented on VELOCITY-504:
---
what?! but that's CRAZY! ;-)
ok, seriously, someone needs
[
http://issues.apache.org/jira/browse/VELOCITY-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461862
]
Nathan Bubna commented on VELOCITY-504:
---
oops. i didn't finish that. it should've read as a corollary
[
https://issues.apache.org/jira/browse/VELTOOLS-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464547
]
Nathan Bubna commented on VELTOOLS-64:
--
John (or others),
Were you ever able to make any headway
[
https://issues.apache.org/jira/browse/VELTOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELTOOLS-58.
--
Resolution: Fixed
ValidatorTool does not respect 'bundle' property for message elements when
[
https://issues.apache.org/jira/browse/VELTOOLS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467249
]
Nathan Bubna commented on VELTOOLS-60:
--
We now have a very simple POM for VelocityTools, but it isn't
[
https://issues.apache.org/jira/browse/VELTOOLS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELTOOLS-66.
--
Resolution: Won't Fix
Ok, i'm not really sure how to resolve this, since a change in Tomcat
[
https://issues.apache.org/jira/browse/VELOCITY-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-515.
---
Resolution: Invalid
Please ask questions about how to use Velocity on the [EMAIL PROTECTED
[
https://issues.apache.org/jira/browse/VELOCITY-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna closed VELOCITY-515.
-
how to handlae velosity projects for open source step by step
[
https://issues.apache.org/jira/browse/VELTOOLS-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473261
]
Nathan Bubna commented on VELTOOLS-77:
--
I have mixed feelings on this. On the one hand, i'm not aware
[
https://issues.apache.org/jira/browse/VELOCITY-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474864
]
Nathan Bubna commented on VELOCITY-518:
---
To my knowledge, Velocity has never released a POM
[
https://issues.apache.org/jira/browse/VELOCITY-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475585
]
Nathan Bubna commented on VELOCITY-519:
---
Thanks, i'll let Will take responsibility for the unicode escapes
[
https://issues.apache.org/jira/browse/VELOCITY-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475897
]
Nathan Bubna commented on VELOCITY-519:
---
The only consensus here is that we should fix the lexer error when
[
https://issues.apache.org/jira/browse/VELOCITY-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-523.
---
Resolution: Fixed
Fix Version/s: 1.5
Unfortunately, i believe
[
https://issues.apache.org/jira/browse/VELOCITY-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479726
]
Nathan Bubna commented on VELOCITY-527:
---
If you are using VelocityEngine.evaluate(...), then you should look
[
https://issues.apache.org/jira/browse/VELOCITY-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479733
]
Nathan Bubna commented on VELOCITY-527:
---
cool. find out anything more about the line column numbers? i'm
[
https://issues.apache.org/jira/browse/VELTOOLS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELTOOLS-79.
--
Resolution: Fixed
Fix Version/s: 2.0
1.x
1.4
[
https://issues.apache.org/jira/browse/VELOCITY-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-499.
---
Resolution: Fixed
Default Velocity LogChute implementations blabber too much
Support varargs in method calls
---
Key: VELOCITY-534
URL: https://issues.apache.org/jira/browse/VELOCITY-534
Project: Velocity
Issue Type: Improvement
Affects Versions: 1.5
Reporter: Nathan Bubna
[
https://issues.apache.org/jira/browse/VELTOOLS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELTOOLS-80.
--
Resolution: Fixed
Fix Version/s: (was: 1.3)
1.4
I've fixed
[
https://issues.apache.org/jira/browse/VELOCITY-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486096
]
Nathan Bubna commented on VELOCITY-536:
---
Looking more carefully at this, rather than trusting my first look
[
https://issues.apache.org/jira/browse/VELTOOLS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486374
]
Nathan Bubna commented on VELTOOLS-81:
--
So, you just copied the saveConvert() method out of the JDK source
[
https://issues.apache.org/jira/browse/VELOCITY-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-519.
---
Resolution: Later
Fix Version/s: (was: 1.6)
2.0
Since
[
https://issues.apache.org/jira/browse/VELOCITY-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486850
]
Nathan Bubna commented on VELOCITY-533:
---
Ok, i've implemented support for size(), isEmpty(), get(int
[
https://issues.apache.org/jira/browse/VELTOOLS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487043
]
Nathan Bubna commented on VELTOOLS-81:
--
Actually, i just did a little investigating. It looks like
[
https://issues.apache.org/jira/browse/VELTOOLS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487053
]
Nathan Bubna commented on VELTOOLS-81:
--
I found the Properties implementation for Harmony:
https
[
https://issues.apache.org/jira/browse/VELTOOLS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELTOOLS-81.
--
Resolution: Fixed
Fix Version/s: 2.0
1.x
1.4
[
https://issues.apache.org/jira/browse/VELOCITY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489435
]
Nathan Bubna commented on VELOCITY-223:
---
Oh, and to finish out my conversation with Lei, he acknowledged
[
https://issues.apache.org/jira/browse/VELOCITY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489434
]
Nathan Bubna commented on VELOCITY-223:
---
Lei has tested and confirmed memory savings, and i see no reason
[
https://issues.apache.org/jira/browse/VELOCITY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489437
]
Nathan Bubna commented on VELOCITY-223:
---
So, all told. I think if we drop the static Map for a ReferenceMap
Components: Engine
Affects Versions: 1.5
Reporter: Nathan Bubna
Assigned To: Nathan Bubna
Fix For: 1.6
When multiple StringResourceLoaders are initialized, the later ones are blowing
up. StringResourceLoader uses a static RepositoryFactory. Unfortunately
[
https://issues.apache.org/jira/browse/VELOCITY-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492313
]
Nathan Bubna commented on VELOCITY-542:
---
This is because '-' is a valid character in a reference.
Try
[
https://issues.apache.org/jira/browse/VELOCITY-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492680
]
Nathan Bubna commented on VELOCITY-542:
---
I should note that i didn't suggest any course of action, because
[
https://issues.apache.org/jira/browse/VELTOOLS-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELTOOLS-82.
--
Resolution: Fixed
Fix Version/s: 2.0
1.4
Thanks, Christopher
[
https://issues.apache.org/jira/browse/VELTOOLS-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494406
]
Nathan Bubna commented on VELTOOLS-82:
--
Oh yeah. Well, the javadoc for StrutsLinkTool.setForward() is a good
[
https://issues.apache.org/jira/browse/VELTOOLS-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494412
]
Nathan Bubna commented on VELTOOLS-82:
--
Thanks again!
StrutsLinkTool.setForward only sees global-forwards
501 - 600 of 1185 matches
Mail list logo