You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Marvin Greenberg <mg...@dctd.saic.com> on 2003/02/26 23:32:26 UTC
missing warnings
Do errors in #if statements get generated properly? I'm using velocity as
an application, and by default am getting info,warn, and errors generated as
I expect for the most part.
But if I have
#if ( $ref.Something() )
where $ref doesn't have a Something method (it has a Something property,
i.e. a getSomething() method) then no warning or error is reported. In
general bad references within an if statement don't seem to get reported.
Now, of course, sometimes I like this behavior, since in another place I say
#if ( $thing.Property ) expecting that some things don't have the property
at all (and I don't want a spurious warning then).
The problem is this allows a certain class of typographical error to go
undetected.
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org
Turn off just [info]?
Posted by marvin greenberg <mg...@dctd.saic.com>.
I'm using the default logger (Avalon LogKit?) with velocity as a
standalone application. I see properties to cause stacktraces for info,
warn and error, but not how to suppress info entirely.
Can someone tell me how to do this?
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org