thanks Ceki, i found the problem. there was slf4j-ext-1.5.something
included along with 1.6-api and 1.6-log4j.
this is the error it caused...
Caused by: java.lang.NoSuchMethodError:
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
at org.slf4j.cal10n.LocLogger.info(LocLogger.java:122)
at
org.jboss.weld.bootstrap.WeldBootstrap.<clinit>(WeldBootstrap.java:213)
thanks for the help,
-igor
On Tue, Aug 16, 2011 at 11:55 PM, 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
>
