"Will Glass-Husain" <[EMAIL PROTECTED]> writes:
>------=_NextPart_000_0035_01C5C4E8.0EFF3430
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>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).
Hm. I'm not really sure about this. There _are_ known
incompatibilities with JDK 1.4 compiled jars under 1.3.
However, the only other package that implements JSR47 for JDK 1.3 that
I know of (Lumberjack Logging) is LGPL, so it is out of the question
to use for compiling. :-(
I do see the advantage of having JDK 1.4 logging in Velocity 1.x. I
know that JDK 1.3 is pretty outdated and no one should use it. But I'm
scared to go to JDK 1.4 here, because our users will expect Vel 1.5 to
be a drop in replacement for 1.4.
>I'm okay with doing this as long as we're careful. Any other comments?
I'm basically -0 on this but I'd like to hear more opinions. It (on a
different level) the same issue as with having a javax.sql.DataSource
dependency (with the difference that there is a jdbc-2.0.jar for JDK
1.3).
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
