[
https://issues.apache.org/jira/browse/LOG4J2-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649088#comment-13649088
]
Nick Williams commented on LOG4J2-109:
--------------------------------------
Yea, I'm going to chime in here and disagree with the notion of having a
combined JAR. A combined JAR will never be right for everyone or even a
majority of folks. For me, the right "combined" JAR would have -api, -core,
-jcl, -slf4j-impl, and -taglib. In general, it just seems like a bad idea to
me. It really isn't that much more work to download the right JARs, it forces
the user to understand Log4j a little better, and it's completely trivial if
you're using Maven.
Having a combined JAR would ultimately result in a lot of confusion and support
issues / bugs because it doesn't contain what one user or another expects.
-1.
> Create an all in one jar
> ------------------------
>
> Key: LOG4J2-109
> URL: https://issues.apache.org/jira/browse/LOG4J2-109
> Project: Log4j 2
> Issue Type: Bug
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> Maven home: C:\Java\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_35, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_35\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
>
> Suggested name: log4j-all-version.jar
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
