[g...@vmgump]: Project velocity-engine (in module velocity-engine) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project velocity-engine has an issue affecting its community integration. This issue

Re: [SURVEY] IntrospectorCache(Listener)

Given the lack of affirmative response, i'm going to take some wild guesses here... On Thu, Jul 24, 2008 at 10:34 PM, Nathan Bubna [EMAIL PROTECTED] wrote: 1) Does anyone out there actually use custom implementations of the IntrospectorCache interface? nope. 2) Does anyone use any

[jira] Commented: (VELOCITY-607) Runtime macro rendering very slow in Velocity 1.6-dev (679708) compared to 1.5

[ https://issues.apache.org/jira/browse/VELOCITY-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12617927#action_12617927 ] Jarkko Viinamäki commented on VELOCITY-607: --- Nathan is right. I have analyzed

[EMAIL PROTECTED]: Project velocity-engine-test (in module velocity-engine) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project velocity-engine-test has an issue affecting its community integration. This

Re: [SURVEY] IntrospectorCache(Listener)

The best way to implement listeners (as you may see in EventListenerList) is to work with arrays.They are immutable and have the lowest memory footprint(instead of HashSet/ArrayList or any concurrent class). Eventually you can skip copying the listeners array if you manage everything locally

[EMAIL PROTECTED]: Project velocity-texen-test (in module velocity-texen) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project velocity-texen-test has an issue affecting its community integration. This issue

[jira] Resolved: (VELOCITY-606) Velocity 1.5 performance bottlenecks

[ https://issues.apache.org/jira/browse/VELOCITY-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Bubna resolved VELOCITY-606. --- Resolution: Fixed Fix Version/s: 1.6 Ok, all patches provided for this issue so far

Re: [SURVEY] IntrospectorCache(Listener)

On Tue, Jul 29, 2008 at 12:36 PM, Adrian Tarau [EMAIL PROTECTED] wrote: The best way to implement listeners (as you may see in EventListenerList) is to work with arrays.They are immutable and have the lowest memory footprint(instead of HashSet/ArrayList or any concurrent class). Eventually

[jira] Commented: (VELOCITY-607) Runtime macro rendering very slow in Velocity 1.6-dev (679708) compared to 1.5

[ https://issues.apache.org/jira/browse/VELOCITY-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12617984#action_12617984 ] Nathan Bubna commented on VELOCITY-607: --- I look forward to seeing your patch,

Re: [SURVEY] IntrospectorCache(Listener)

Actually I forgot something : addListener and removeListener needs to be synchronized(we don't want to loose a change), but not fireEvent(we just use the current array). Nathan Bubna wrote: On Tue, Jul 29, 2008 at 12:36 PM, Adrian Tarau [EMAIL PROTECTED] wrote: The best way to implement

Re: [SURVEY] IntrospectorCache(Listener)

Nathan, That seems fine to me. If they are slowing down performance, let's put the onus on the user/contributor to improve them. (It's not clear that the feature actually has users). WILL On Tue, Jul 29, 2008 at 4:47 PM, Adrian Tarau [EMAIL PROTECTED] wrote: Actually I forgot something :

[EMAIL PROTECTED]: Project velocity-engine-test (in module velocity-engine) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project velocity-engine-test has an issue affecting its community integration. This