Replies: 2 comments
-
Can you specify the OS, JDK version where this issue occurs? A test case would be most appreciated. The test case can omit using logback, and involve only the |
Beta Was this translation helpful? Give feedback.
0 replies
-
@ceki thanks for your answer. I did more tests and I realized that it was Gradle messing around with me. We have multiple modules inside one repo and running gradle from the root of the repo. Some commands had different cwd (of the module) and that's why it was failing. I managed to fix it on our end. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am using LogBack in the company I work for and we encountered an issue with it. The problem is that in line 58 of
FileUtil
there is a call toparent.exists()
, but that returns false if the path is relative. I didn't arrive to the source of the problem, I was trying to set-Duser.dir
as is suggested here but it doesn't help. However I see that something like this works:in the image you can see the variables from my debugger:
As you can see the
user.dir
is correct but still theexists()
on relative file is failing.What do you think about changing that to use
getAbsoluteFile()
? Do you see anything against? Or maybe you have an idea how to fix it on our side? I'm happy to make this change and prepare PR if needed.Beta Was this translation helpful? Give feedback.
All reactions