Commons Logging deprecated? was Re: [logging] 1.1.1 release?
On Sat, 2007-03-10 at 16:05 +1300, Simon Kitching wrote: On Sat, 2007-03-10 at 03:38 +0100, Torsten Curdt wrote: Definitely happy to give M2 a try; but I'd rather not change the groupId on a bugfix release. We already have an M2 release in FileUpload that didn't change the groupid so that's not a worry. Plus I want to get it done quickly :) Ah ...my +1 for changing the groupId was not meant for this bugfix release. It would be good to change it for new major releases though. I expect that this will be the last ever release of commons-logging. There are no features missing, no known bugs, and as support for java 1.4 is now generally universal there is no reason for applications not to use the java.util.logging API directly. Hi Simon, This is a little bit of a shocker to me. Does your opinion represent the collective opinion of the JCL developers? Do I interpret your message correctly that JCL has been effectively deprecated, there will be no work done toward JCL 2.0 and the upstream projects that currently depend on JCL are advised to migrate to JUL? Cheers, Oleg Note that java.util.logging is an *API*, and the implementation bundled in Sun's jdk is not the only choice (see JULI for example). Changing the group-id is something that can only be done on a release, so it seems sensible to do it for 1.1.1 even if this is just a bugfix release. Cheers, Simon - 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]
Re: Commons Logging deprecated? was Re: [logging] 1.1.1 release?
Oleg Kalnichevski [EMAIL PROTECTED] wrote: On Sat, 2007-03-10 at 16:05 +1300, Simon Kitching wrote: I expect that this will be the last ever release of commons-logging. There are no features missing, no known bugs, and as support for java 1.4 is now generally universal there is no reason for applications not to use the java.util.logging API directly. This is a little bit of a shocker to me. Does your opinion represent the collective opinion of the JCL developers? Do I interpret your message correctly that JCL has been effectively deprecated, there will be no work done toward JCL 2.0 and the upstream projects that currently depend on JCL are advised to migrate to JUL? It's only my personal opinion. However I am one of the major contributors to JCL since 1.0.4. There is nothing *wrong* with JCL, and the code isn't going to be removed from the Apache servers. And if there are any significant bugs found they are likely to be fixed. So there's no need to be worried, or to rush off to change any existing code. However if code requires java1.4 or later for other reasons I don't see any benefit in that code using JCL; the java.util.logging api is built in to java so why download an additional jar? For libraries that still want to support java1.3 or older, JCL is an excellent choice. However that's a rapidly shrinking category. Apache Tomcat now requires java1.4, and has moved to java.util.logging as its API (with JULI as the underlying implementation); I would suggest other code do the same. I did spend some time and effort researching possible JCL 2.0 designs, but after further thought decided there was little point. Of course I'm only speaking for myself here. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
