Well I knew it must have been something entirely dumb - as it turns out an NPE was stopping my logging statements from being executed (duh!). This was a case of looking in the wrong place ... I've had various problems with M2 plugins so I guess I was too quick to assume it was something to do with surefire. Sorry for the trouble and thanks for your advice.
As a side question - and please forgive me labouring the point but it's still not obvious to me - when you say you include your log4j configuration as part of the server configuration, you would still need to deploy to (say) a web container in a testing environment that's different from your live server, so however it's configured the details may change. I still can't see how you would automate this for deployment to both a development and live environment without some sort of build switch (e.g. "mvn -Denv=live [...]") and then decisions based on that - though I take your point about wanting to avoid any classloader wars. I guess what I'm asking is, if you have the time to elaborate on what you mean, I'd be interested to hear what you say. Thanks ... Toni -- View this message in context: http://www.nabble.com/-M2--log4j-output-does-not-display-when-running-surefire-plugin-t1747117.html#a4755965 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
