Hello Zoltan, Good suggestion. I'd appreciate if you could create a jira issue for it.
Szel, Zoltan (IT) wrote: > Hi all, > > i have hit this issue a couple of times now, so i go ahead and rise it. > > We are creating libraries to our developers, which are usually have an > example part, where they can try our piece of software out. These > examples are part of our Eclipse project. All these examples have a > logback.xml file to show how a complete application should look like. > During development, this causes some issues because the first one in the > classpath will be loaded, so i ended up to use the manual config loading > via Joran, but it took me some time to figure out the root cause of the > issue. I imagine, this will cause issues when developers will start to > bundle there logback.xml file into there jars. > > Could the ContextInitializer be changed to detect such a scenario and > report it? The change is fairly easy, instead of using the > getResource(String name) function from the ClassLoader class, you could > go with the getResources(String name) function, check if it returned > more than one element, than report to the Status manager the fact, that > there are more than 1 logback.xml file on the classpath and the first > one will be used. > > Thanks in advance, > > Kind Regards, > Zoltan Szel -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ logback-dev mailing list [email protected] http://qos.ch/mailman/listinfo/logback-dev
