[JIRA] [maven2] (JENKINS-17640) Maven3-agent complains about incorrectly configured log4j

[jenkins-ci....@waisbrot.net (JIRA)]

Nathaniel Waisbrot created JENKINS-17640 Maven3-agent complains about incorrectly configured log4j Issue Type: Bug Assignee: Unassigned Components: maven2 Created: 16/Apr/13 8:35 PM Description: 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. Project: Jenkins Labels: logging configuration maven Priority: Trivial Reporter: Nathaniel Waisbrot

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.