Thanks for ongoing input.
No can do ( getCause() ) for 1.5, unfortunately. Though I agree it would be
useful. (as
would using JDK regexps, and lots more).
It's important Velocity 1.5 remain a drop-in replacement for all users.
Some of those users might have 1.3 at runtime. We need to continue
supporting this. It's not cool to insist that a user upgrade their app
server just to accomodate a single library.
This suggestion (1.4 compiletime) only works for plugin code that will not
be executed by default at runtime.
WILL
----- Original Message -----
From: "Llewellyn Falco" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <velocity-dev@jakarta.apache.org>
Sent: Thursday, September 29, 2005 1:29 PM
Subject: Re: Quick Poll: compile-time requirement for JDK 1.4?
I'm all for the 1.4!
1.3 is pretty out of date nowadays.
In particular, i would like the functionality of
Exception.getCause() for when an exception is thrown in a method call.
llewelyn.
----- Original Message -----
From: "Will Glass-Husain" <[EMAIL PROTECTED]>
To: <velocity-dev@jakarta.apache.org>
Sent: Thursday, September 29, 2005 11:22 AM
Subject: Quick Poll: compile-time requirement for JDK 1.4?
Hi,
Nathan's proposed adding a compile time requirement for JDK 1.4. (as part
of VELOCITY-403).
This would allow us to use include JDK 1.4 features (like JDK logging) as
pluggable options. Velocity would still run under JDK 1.3 as long as the
feature was pluggable and not the default (like JDK Logging).
I'm okay with doing this as long as we're careful. Any other comments?
Best, WILL
_______________________________________
Forio Business Simulations
Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
