Not quite sure what you mean by a debugger. Do you mean a mechanism
to see problems in a Velocity page?
For parse errors, Velocity 1.5 throws an Exception providing the line
number, column number, and template name of the error. The Click
framework uses this info to do a nice job of
[
https://issues.apache.org/jira/browse/VELOCITY-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467504
]
Mailmur commented on VELOCITY-191:
--
Good catch this UTF16-LE / UTF-32LE issue, thx.
Yes, I studied this
Sorry, wrong thread. let's try that again...
On 1/25/07, Nathan Bubna [EMAIL PROTECTED] wrote:
The vote has passed! I'll tag the release today and try to upload it
tonight or tomorrow. Announcement should follow once the release is
mirrored.
PMC +1
Nathan Bubna
Will Glass-Husain
Henning
Hi Henning,
+1, with a caveat...
Users will want to see specifics of what's new with the system.
Where's the change list? Will Maven generate this automatically? I
suggest we have two items
* a copy of the release notes from the Wiki, moved into the main
distro as RELEASE-NOTES.txt. This
