Jeppe Nejsum Madsen wrote:
On Tue, Aug 18, 2009 at 6:14 AM, Adam Murdoch<[email protected]> wrote:
Jeppe Nejsum Madsen wrote:
On Sat, Aug 15, 2009 at 5:50 AM, Adam Murdoch<[email protected]> wrote:
This should be fixed in trunk now. Could you give it a try?
Just tried with the new scala plugin merged and it works! Get a
warning since I also use slf4j in the webapp:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/Users/jeppe/projects/gradle/trunk/build/distributions/exploded/lib/logback-classic-0.9.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/Users/jeppe/.gradle/cache/ch.qos.logback/logback-classic/jars/logback-classic-0.9.17.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
Not sure what the best solution for this is......
Where and when is the warning getting logged? eg, which task is running?
Does it get logged to the console?
It's when the jettyRun task is running and (I assume) the webapp with
the other SLF4J binding is started. It is being logged to the console.
One more note with regards to logging, not sure if this is related to
these fixes, but I dont' remember seeing them before: It looks like
the output from Gradle when downloading is not in the correct order,
see below where e.g. the download messages are logged (to the console)
after the jettyRun task is started:
(also seems like the jars are downloaded several times, see e.g.
lift-util-1.1-SNAPSHOT.jar. Not sure if this is happening or just the
logging that is repeated)
I will have a look at these soon. Does everything work ok, and these
just annoying? Or is something broken?
Adam
