Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17640

Maven3-agent complains about incorrectly configured log4j

XMLWordPrintable

      When starting a Maven build, the maven3-agent.jar produces a log4j warning that it hasn't been configured:

      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
<===[JENKINS REMOTING CAPACITY]===>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

      Work-around: adding a log4j.xml configuration file to the root of the maven3-agent.jar corrects this problem.

            Unassigned Unassigned
            waisbrot Nathaniel Waisbrot
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: