Hi, I just fixed the SLF4J dependencies. Now they are again 1.6.1.
Now there is a problem in wicket-examples - trying to start them fails with "java.lang.UnsupportedClassVersionError: Bad version number in .class file" It seems we have third, bigger problem :-) javax.enterprise.** (and weld I guess) seems to compiled with JDK1.6 On Wed, Aug 17, 2011 at 9:55 AM, Ceki Gülcü <[email protected]> wrote: > > >> i had to downgrade slf4j to 1.5 from 1.6. weld uses 1.5 and its >> binary-incompatible with 1.6. i forgot to start a vote because i made >> a change a while back and forgot about it when committing. if i can >> resolve issue #1 i will start a vote on this one. > > Hi Igor, > > Code compiled with SLF4J will run with any version of slf4j-api.jar because > all versions of slf4j-api are mutually compatible. It's the bindings which > are version sensitive. See also [1]. > > Unless weld ships with its own copy of slf4j-1.5.jar bundled in or packages > slf4j-api in an unusual way, you should be able to use slf4j-api-1.6.1.jar > with weld. Just make sure that the version of the slf4j binding matches. > > HTH, > -- > QOS.ch, main sponsor of cal10n, logback and slf4j open source projects, is > looking to hire talented software developers. For further details, see > http://logback.qos.ch/job.html > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
