Good Morning,
Jacob Kjome wrote:
For those not willing or able to move past JDK1.3, it seems like
they'd also be unlikely to keep up with the latest versions of
supporting libraries such as Log4j.
+1 !!!
Since the 1.2.xx branch will always be there and still works just
fine, I don't see any problem with moving to JDK1.4, as long as
application code that had used 1.2.xx continues to work with 1.3.xx
when the user makes the move to JDK1.4+. A 2.xx release should
definitely move to 1.5 after that, as long as there's a compelling
reason to do so.
yes, exactly.
Full maintenance (Bug fixing, support, bug fix releases) for log4j 1.2.12 for JDK 1.2.x Users
Actual (trunk) release, compatible for application code with log4j 1.3 for JDK 1.4.x Users (source 1.4, target 1.4).
I have voted for JDK 1.3, but this was based on the argument of a user base.
Jacob's argumentation is more important to me than the absolute/relative count of potential users.
This is also based on my own experience: My company is not willing to move from 1.2.8 to 1.2.13
due to the argument "never change a running system" and they have moved from IBM JDK 1.3.? to 1.4.2
Regards
Boris
