title: Jenkins slave running Maven gives log4j warning
body: <p>I'm using Jenkins, and I have a Windows machine set up as a slave worker.  I have a Maven-based project that runs on the slave.  The build works correctly, but I get a warning from log4j about it not being initialized.  I'd like to scratch that itch and remove the warning, but I don't know how.  </p>
  
  <p>I'm not very familiar with log4j.  I do understand I could set a system property to tell it where to find a config file, but I don't know where in the Jenkins pipeline that property should be set or how.  It looks like the warning comes before Maven starts but after the slave begins the job.</p>
  
  <p>Here's the snippit of console output:</p>
  
  <pre><code>Parsing POMs
  [MyTest] $ java -cp C:\jenkins\maven3-agent.jar;C:\jenkins\tools\Maven\Maven\boot\plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main C:\jenkins\tools\Maven\Maven C:\Users\waisbrot\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\28\5c50da9c-2d1a9aef C:\jenkins\maven3-interceptor.jar 49210
  &lt;===[JENKINS REMOTING CAPACITY]===&gt;channel started
  log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
  log4j:WARN Please initialize the log4j system properly.
  Executing Maven:  -B -f C:\jenkins\workspace\MyTest\pom.xml test
  [INFO] Scanning for projects...
  </code></pre>