http://bugzilla.slf4j.org/show_bug.cgi?id=31
--- Comment #58 from boci <boci.b...@gmail.com> 2009-11-14 20:08:06 --- (In reply to comment #56) > Sorry, I was not clear in my previous response. I had understood that > the use of the new logger was optional which is the point of keeping > the old one untouched. > > The issue is about educating users as much as it is technical. Users > would need to be educated about the two different slf4j loggers. I > suspect we would run into technical issues as well (while trying to > juggle between the two Logger implementations). > > By the way, we already have a solution for varargs issue as long as we > agree to bump the JDK dependency to 1.5. See my comment #31 above > dated 2009-03-25. It offers a transparent upgrade path. Replace the > older slf4j-api.jar with the latest version and get varargs support > for free. Existing code is both compile time and runtime compatible. > Disagree. Runtime compatibility is not required. Java 1.4 is dead. I think only bugfix release need for 1.4 compatible slf4j. I think two simple step required: - Change major version to 2.x - Change Object[] to Object... in api and implementations method signatures. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dev mailing list dev@slf4j.org http://www.slf4j.org/mailman/listinfo/dev
