„GroboUtils-5-core.jar“ contains log4j property file in his root. This was causing logging problems in our tests if log4j.property file from „GroboUtils-5-core.jar“ was loaded by log4j
initialization logic before our own log4j.properties file (which is located in test scoped classpath). It take me some time to figure out why my logging not works as espected. I think that putting log4j.properties file in jar is not the best practice.
We have bypass problem by setting log4j.configuration system property.
Aldo this is not some serious issue I wanted to inform you about the problem we encounter which can save time to people encountering the same problem.