DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43452>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43452 Summary: Several dependencies not optional in pom.xml Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Other AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Please consider marking several dependencies in the log4j maven pom.xml as optional. http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html We recently attempted to update our log4j version in our own maven projects from 1.2.13 to 1.2.15 to take advantage of the XMLLayout updates. Upon doing so, we noticed that log4j itself became mavenized and now specifies dependencies such as: - com.sun.jdmk: jmxri - com.sun.jmx: jmxtools For those of us who don't use the jmx features of log4j, this forces us to either include com.sun libraries in our artifacts (such as webapps). As a workaround we can exclude this from our own pom.xmls but since maven provides the optional tag, please consider using it for these com.sun dependencies. Log4j has existing in public maven repositories for years. It seems odd that the 1.2.x branch now all of a sudden has extra required dependencies. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
