Re: Engine 1.6.2?

Sure, but not before something like January 10th if I do care about it. Claude On dim, 2008-12-28 at 09:31 -0800, Nathan Bubna wrote: > given the $velocityHasNext issues, i think we should do another bugfix > release. i'm willing, but if someone else is interested/willing then > i'd be happy

[jira] Created: (VELOCITY-660) consider moving logging (and errors?) to an event/monitor approach

consider moving logging (and errors?) to an event/monitor approach -- Key: VELOCITY-660 URL: https://issues.apache.org/jira/browse/VELOCITY-660 Project: Velocity Issue Type: Imp

[jira] Resolved: (VELOCITY-168) RFE: switch to commons-logging

[ https://issues.apache.org/jira/browse/VELOCITY-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Bubna resolved VELOCITY-168. --- Resolution: Won't Fix > RFE: switch to commons-logging > -- > >

[jira] Commented: (VELOCITY-168) RFE: switch to commons-logging

[ https://issues.apache.org/jira/browse/VELOCITY-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659495#action_12659495 ] Nathan Bubna commented on VELOCITY-168: --- Well, we're definitely not moving to commo

[jira] Created: (VELOCITY-659) Remove throwing Exception from method signatures

Remove throwing Exception from method signatures Key: VELOCITY-659 URL: https://issues.apache.org/jira/browse/VELOCITY-659 Project: Velocity Issue Type: Improvement Components: Engin

[jira] Commented: (VELOCITY-168) RFE: switch to commons-logging

[ https://issues.apache.org/jira/browse/VELOCITY-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659493#action_12659493 ] Byron Foster commented on VELOCITY-168: --- Can we close this issue? It seems like the

[jira] Resolved: (VELOCITY-655) Macro parameter value can't be changed inside a macro

[ https://issues.apache.org/jira/browse/VELOCITY-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Bubna resolved VELOCITY-655. --- Resolution: Fixed Fix Version/s: 1.6.1 Yes. :) > Macro parameter value can't be cha

[jira] Commented: (VELOCITY-655) Macro parameter value can't be changed inside a macro

[ https://issues.apache.org/jira/browse/VELOCITY-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659453#action_12659453 ] Jarkko Viinamäki commented on VELOCITY-655: --- If this has been fixed, should it

[jira] Resolved: (VELOCITY-658) $velocityHasNext does not work in nested loops

[ https://issues.apache.org/jira/browse/VELOCITY-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarkko Viinamäki resolved VELOCITY-658. --- Resolution: Fixed Fix Version/s: 1.7 > $velocityHasNext does not work in nes

[jira] Reopened: (VELOCITY-658) $velocityHasNext does not work in nested loops

[ https://issues.apache.org/jira/browse/VELOCITY-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarkko Viinamäki reopened VELOCITY-658: --- > $velocityHasNext does not work in nested loops >

[jira] Resolved: (VELOCITY-658) $velocityHasNext does not work in nested loops

[ https://issues.apache.org/jira/browse/VELOCITY-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarkko Viinamäki resolved VELOCITY-658. --- Resolution: Fixed Thanks. Marking this as resolved. > $velocityHasNext does not wo

Engine 1.6.2?

given the $velocityHasNext issues, i think we should do another bugfix release. i'm willing, but if someone else is interested/willing then i'd be happy to let them drive the process. any takers? - To unsubscribe, e-mail: dev-un

[jira] Commented: (VELOCITY-658) $velocityHasNext does not work in nested loops

[ https://issues.apache.org/jira/browse/VELOCITY-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659422#action_12659422 ] Byron Foster commented on VELOCITY-658: --- Applied, thanks > $velocityHasNext does n