You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Nathan Bubna (JIRA)" <de...@velocity.apache.org> on 2010/08/31 18:08:53 UTC
[jira] Resolved: (VELTOOLS-129) DisplayTool does not call
super.configure
[ https://issues.apache.org/jira/browse/VELTOOLS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELTOOLS-129.
-----------------------------------
Fix Version/s: 2.0.x
2.x
Resolution: Fixed
Fixed, thanks. And just so you know, "Blocker" is for things that break the VelocityTools build or otherwise prevent us from doing a release. The priorities refer to the importance of the bug to VelocityTools, not to your application. :)
> DisplayTool does not call super.configure
> -----------------------------------------
>
> Key: VELTOOLS-129
> URL: https://issues.apache.org/jira/browse/VELTOOLS-129
> Project: Velocity Tools
> Issue Type: Bug
> Components: GenericTools
> Affects Versions: 2.0
> Reporter: Michael Osipov
> Priority: Blocker
> Fix For: 2.0.x, 2.x
>
> Attachments: displaytoo-locale.patch
>
>
> I recently used the DisplayTool and had weird results. Traced the issue down and noticed that in contrast to ResourceTool on this [line http://svn.apache.org/viewvc/velocity/tools/tags/2.0/src/main/java/org/apache/velocity/tools/generic/DisplayTool.java?view=markup#l153] super.configure is not called. DisplayTool has always the same locale as the JVM. I have created a patch which works as desired.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org