, how it will be great to have a eclipse debugger for the RCP
application.
That's why I'm interrested to have this velocity debugger !!
Well, I began to work on that, but I have touch the velocity 1.4 code, and
put some code in the render methods, and I know that you have generated with
JavaCC
for the RCP
application.
That's why I'm interrested to have this velocity debugger !!
Well, I began to work on that, but I have touch the velocity 1.4 code, and
put some code in the render methods, and I know that you have generated with
JavaCC, but I've no time to do it with JavaCC, that's why I came
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Velocity-Debugger-tf3081966.html#a8700326
Sent from the Velocity - Dev mailing list archive
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
