Closed aguslarla closed 5 years ago
As you noticed, the file is where it is supposed to be, so I don't think ELKI is to blame here.
But you most likely have a modified class loader setup, and that is where the problem supposedly is.
Hi Erich!
Thanks for your fast answer. I am going to review my code carefully but at simple view, i don´t see nothing wrong.
It likely is not obvious in the code; but rather a question of how it is launched (in particular, of the classpath and class loader). For example, building fat jars could break this. The screenshot you shared indicate that there is at least some other logging framework loaded that could also cause interference.
The packaged logging.properties is loaded via ClassLoader.getSystemResourceAsStream
, and that can break with custom class loading.
In the latest version 0.7.5, this will use the classes own classloader, which is much more reliable:
As a workaround you can simply try to provide a customized logging.properties file.
Hi! I apologise for disturbing if i am wrong for openning this issue here.
I am using Elki v.0.7.1 library in my project and i am obtain the message in subject issue. I have checked the library and the "logging.properties" file exists.
I attach two screenshots with the issue.
I hope your answer. Thanks a lot.
![elki_library](https://user-images.githubusercontent.com/13064163/54029386-7e40d500-41a8-11e9-89f7-4c46b1a9cd9d.png)