Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silence webjars logging during compilation #132

Open
joprice opened this issue Jan 18, 2016 · 5 comments
Open

Silence webjars logging during compilation #132

joprice opened this issue Jan 18, 2016 · 5 comments

Comments

@joprice
Copy link

joprice commented Jan 18, 2016

I see tons of debug logging coming from org.webjars.WebJarExtractor. I would think putting a logback.xml in project/src/main/resrouces would let me control it, but that doesn't seem to work.

21:39:16.422 [pool-14018-thread-3] DEBUG org.webjars.WebJarExtractor - Checking whether META-INF/resources/webjars/jquery/2.1.4/src/var/hasOwn.js is up to date at...
@reid-spencer
Copy link

+1 - This is obfuscating behavior of sbt-web and I don't see a way to defeat it.

@huntc
Copy link
Contributor

huntc commented Apr 16, 2016

I think that this is an issue for WebJars. I'm not seeing it though. Is it still a problem for you?

@joprice
Copy link
Author

joprice commented Apr 16, 2016

At this point, I'm not sure which project I found it in. I'll have to poke around and get back to you.

@reid-spencer
Copy link

I recently resolved this problem in a project by straightening out all the SLF4J warnings and logback configuration. In my case I had a file named "logging.xml" that should have been "logback.xml". As soon as I renamed the file, those messages went away (and many others too). The problem, I think, is that in the absence of any log levels being defined or SLF4J having a resolved logger, the webjar library defaults to debug level and you get the verbosity .. or something like that (I didn't look into the details once it was fixed). Just thought this anecdote might help track it down.

@vito-c
Copy link

vito-c commented May 24, 2019

I think this could be related to SLF4J not resolving the correct logger but for me it only happens at compile time and is only with this specific package org.webjars.WebJarExtractor. I've added everything correctly to my logback.xml but it doesn't look like sbt-web respects my logabck.xml or possibly that it's not loaded yet?

I attached a debugger to this and dug pretty deep. The interesting thing is that it only happens with test:compile it doesn't happen with compile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants