Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MAVEN-1481 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-1481 Summary: Dependency.getId pukes if log4j set to DEBUG Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Versions: 1.0 Assignee: Reporter: Matthew Daniel Created: Thu, 28 Oct 2004 6:37 PM Updated: Thu, 28 Oct 2004 6:37 PM Environment: Win2k, J2SE 1.4.2_05, maven 1.0 downloaded from maven.apache.org Description: I was trying to diagnose what was wrong with the HttpDeployer, and saw that it logs its exception, but only at DEBUG level. So I created a new log4j.properties and overrode the log4j classpath setting with -Dlog4j.configuration=file:log4j.properties. So far, so good. But Maven would never parse a plugin's project.xml again, failing with: java.lang.IllegalStateException: either id or (groupId and artifactId) must be provided for a dependency at org.apache.maven.project.Dependency.getId(Dependency.java:116) I switched org.apache.commons back to INFO (or anything except DEBUG) and it works great. I understand this may not be entirely a Maven problem, since the logger is org.apache.commons but if Maven is dying, I thought you guys would want to know about it. I shall attach the complete output. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
