http://bugzilla.slf4j.org/show_bug.cgi?id=31
Ceki Gulcu <lis...@qos.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lis...@qos.ch
--- Comment #30 from Ceki Gulcu <lis...@qos.ch> 2009-03-25 12:02:11 ---
As I already wrote in comment #24, given the large number of SLF4J users, we
just can't make any incompatible changes, especially if they involve intricate
technical details. Even mundane assumptions such as slf4j-api.jar version
matching the binding version have proven to be too optimistic [1,2].
You see, the JDK version people use is irrelevant. Even if every single
developer in the world used JDK 1.7, SLF4J would still need to stick to the
current API. Otherwise, people would run into compatibility problems involving
SLF4J itself. If in your project P you imported library L0 and library L1, and
if L0 relied on SLF4J version n and L1 relied on SLF4J version m, and if for
any reason n and m were incompatible, you'd be facing an intractible problem.
There seems to be too high a risk to introduce incompatibility at such a high
level of the SLF4J API. Let me give it a fresh look and come back with further
conclusions.
[1] http://slf4j.org/faq.html#compatibility
[2] http://slf4j.org/faq.html#IllegalAccessError
--
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
