> I tend to think the underlying problem (two slf4j-log4j12 jars on the
> classpath) is in SBT, so maybe you should ask on the sbt list.
Ya, I'm pretty sure you're right. I posted there:
http://groups.google.com/group/simple-build-tool/browse_thread/thread/4d088713c85dbdb
-harryh
--
You r
On Thu, Mar 4, 2010 at 9:21 PM, harryh wrote:
>> Hmm, slf4j-log4j12-1.5.11.jar ends up being in the classpath twice (from
>> /Users/harryh/foursquare.web/lib_managed/compile and
>> /Users/harryh/foursquare.web/target/webapp/WEB-INF/lib).
>>
>> A quick fix would be to apply exclusion of slf4j-log4j
> Hmm, slf4j-log4j12-1.5.11.jar ends up being in the classpath twice (from
> /Users/harryh/foursquare.web/lib_managed/compile and
> /Users/harryh/foursquare.web/target/webapp/WEB-INF/lib).
>
> A quick fix would be to apply exclusion of slf4j-log4j12 in lift-util
> declaration. This will prevent hav
On Thu, Mar 4, 2010 at 8:35 PM, harryh wrote:
> OK, did that (like so in sbt):
>
> override def ivyXML =
>
>
>
>
>
>
> I'm also getting this error when running my app from within sbt just
> javarebel (possibly this isn't a big issue, but the error is
> disconcerting):
>
On 05/03/10 1:05 AM, harryh wrote:
OK, did that (like so in sbt):
override def ivyXML =
I'm also getting this error when running my app from within sbt just
javarebel (possibly this isn't a big issue, but the error is
disconcerting):
Hmm, slf4j-log4j12-
OK, did that (like so in sbt):
override def ivyXML =
I'm also getting this error when running my app from within sbt just
javarebel (possibly this isn't a big issue, but the error is
disconcerting):
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found
