You're right, I overlooked that, but your output didn't show the source paths at
all for mvn - just for eclipse.
Ondřej Černoš on 22/10/07 13:25, wrote:
thanks for quick answer. The target/classes directory contains the
production log4j.properties file. I always thought maven uses the
target/t
Hi Adam,
thanks for quick answer. The target/classes directory contains the
production log4j.properties file. I always thought maven uses the
target/test-classes directory as the classpath entry during the tests
- it contains the correct version of the log4j.properties file, but it
seems the targe
Hi Ondrej
looks like mvn is not only picking up the production log4j.properties file but
it's also probably not substituting ${catalina.home}
Check in your target/classes directory for log4j.properties and see if it's
substituted it.
Secondly, log4j uses the first log4j.properties it comes
Hi,
I am experiencing a problem with testing and resources. Basically, it
seems the production and not the test resources are used when running
tests.
I have two log4j.properties files, one defines appender as file
appender in src/main/resources:
log4j.appender.dest1=org.apache.log4j.RollingFile
