http://bugzilla.slf4j.org/show_bug.cgi?id=31
------- Comment #27 from [EMAIL PROTECTED] 2008-05-08 14:38 ------- (In reply to comment #22) > For instance, the Geronimo project just switched to SLF4J. What if > Geronimo exported slf4j-api while some application was expecting > slf4j-api-jdk15? Getting off-topic, but it's a horrible practice for an app server to expose it's implementation classes and libraries to applications. I really hope that would be banned in the next spec revision. I would vote dropping JDK 1.4 support and bumping version to 2.0. I agree having same implementation under different artifactId has a high potential for problems (especially considering maven limitations in that respect). How about posting a query to users-list about the subject? (just a proposal - if your decision is final then it's final, and we have to accept that). But in that case, will sfj4j support JDK 1.4 for the the foreseeable future? -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ dev mailing list dev@slf4j.org http://www.slf4j.org/mailman/listinfo/dev
