Bernd Fondermann wrote:
We should continue to make sure James is running with Java versions > 1.4 And I am +1 for a future version of the mailet engine to require Java 5. About requiring Java 5 for the Server, I don't know. Why should the Server require Java 5 if it really does not use any J5 specifics and only one of its subprojects does?
I think we don't require Java 5 simply because we chose to not use java 5 features :-) . I bet that if we start requiring java 5 then we'll soon see generics, @override, enum and other useful stuff all over the code.
Furthermore java 5 would give us MINA for SSL/StartTLS support: our current SSL support break sun jre 6 compatibility: I've not investigated on this but if this is the case I would prefer to loose java 2 1.4 compatibility in favor of java 6 compatibility for next-greater. (Mina seems to provide a vendor indipendent solution, while our current ssl support seems to be bound to SUN jdk 1.4 and 1.5 only).
Btw I think it is a matter of time: sooner or later java 5 requirement will not be an issue anymore.
If the mailet engine was pluggable and a J1.4 compatibility release was available, it would not be such a big shift.
If we place varargs logging methods in the next mailet apis then implementors of that API will need java 5. So this not only "1 subproject require J5 specific stuff" but we don't need the main project to do the same.
Is there any statistic site that can tell us what is the standard delay in JVM adoption?
Does anyone know how many users was on Jdk 1.3 for outdated j2ee servers 1 year after java 5 has been released?
Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
