On 25 Feb 2015, at 16:35, Till Rohrmann wrote:
> The reason for this behaviour is the following:
>
> The log4j-test.properties is not a standard log4j properties file. It is
> only used if it is explicitly given to the executing JVM by
> -Dlog4j.configuration. The parent pom defines for the sur
The reason for this behaviour is the following:
The log4j-test.properties is not a standard log4j properties file. It is
only used if it is explicitly given to the executing JVM by
-Dlog4j.configuration. The parent pom defines for the surefire plugin a
corresponding argument line with this option.
Hey Flinksters and IntelliJers, ;-)
the tests resources directory of each Maven module contains a
log4j-test.properties files, which gets picked via the classpath by JUnit
tests, but not Scalatest. Instead Scalatest picks up log4j.properties, but
JUnit doesn't.
It works when I specify the file
