-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
Works great but getting Output is throwing an error. #60
Comments
I've seen this happen to me rarely. Usually rerunning it fixes it. You may want to restart your IDE or refresh your dependencies to get it to pick up. |
Haven't heard back on this. LMK if this addresses your issue or not. Otherwise, I will close this out. |
Sorry for the delay, I tried to few times to restart times to the IDE and also reload the dependencies and I was getting the same error. I am using VS code, and it could probably be related to that but what ended up working for me was changing this code in the build.sbt file: "org.apache.logging.log4j" % "log4j-core" % "2.13.0",// % Runtime, |
That is interesting. I'll try messing with it a bit. As long as it works with sbt then I think it's fine since that is the "Scala way". The |
So this is the documentation where I determined how to pull down the log4j dependencies 👉 https://logging.apache.org/log4j/scala/index.html No one else has reported the issue so I'm going to leave it as is for now. There were a few version bumps since you last reported this so I'll probably make a small fix and see if that changes anything. If it's still acting weird for you, feel free to LMK. |
Made a PR to merge in the version bump changes 👉 #85 |
First off, love this works great!
I get this error when running "ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console..."
It appears that the only thing is impacts is the debug/output. any thoughts on what would resolve it? it would be very nice to see success/failures
Thanks again!
The text was updated successfully, but these errors were encountered: