You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2007/09/05 06:22:09 UTC

DO NOT REPLY [Bug 43304] - Maven POM dependencies

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=43304>.
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=43304





------- Additional Comments From carnold@apache.org  2007-09-04 21:22 -------
Background info: http://maven.apache.org/guides/introduction/introduction-to-optional-and-
excludes-dependencies.html

Neither optional dependencies or exclude dependencies (which could be used as a work-around with 
1.2.15) are desirable.  But log4j 1.2.x isn't a candidate to be split into subprojects with only non-
optional dependencies.

The log4j 1.2.14 POM (and likely proceeding ones) were not actually used to build log4j and listed no 
dependencies (or effectively everything was an optional dependency).

I could see how it would be desirable to make the compile scope dependencies (javamail, jms, jmxri, 
jmxtools) optional in 1.2.16.  Or maybe all but javamail since it is in java.net repo and is more likely to 
be used than the others which need to be manually downloaded.


-- 
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org