Skip to content
This repository has been archived by the owner on Mar 1, 2021. It is now read-only.

src/main/resources/log4j.xml overriding client log configuration #27

Closed
SausagePie opened this issue May 26, 2015 · 3 comments
Closed

Comments

@SausagePie
Copy link

The src/main/resources/log4j.xml is interfering with my own logging configuration.
Suggest that you move your log4j.xml to src/test/resources.

Log4j attempts to load log4j.xml first, and then log4j.properties, using the first it finds on the classpath.

I have my own logging configuration (log4j.properties). Your log4j.xml is being picked up instead.

I can workaround it, but this is something you might like to clean up.

Some related discussion:
http://stackoverflow.com/questions/10890505/multiple-log4j-properties-files-in-classpath?rq=1

@karussell
Copy link
Member

Okay, related to graphhopper/graphhopper#250

@devemux86
Copy link
Contributor

I'd vote for that too.

Also somehow related to graphhopper/graphhopper#494.

@karussell
Copy link
Member

Will be fixed with graphhopper/graphhopper#1334

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants