I would LOVE that. I've stopped and started this a couple of times but always got side tracked with other tasks and shifting needs for what *all* means because it does not means "all" jars since that would cause a loop.
The issue is what to include and what to exclude... For example, why not include nosql and io-streams? For me, today, my "all" is to provide customers Log4j2 with *all* appenders, so that they can go to town on configuring events to go anywhere Log4j supports. Integration with other frameworks is a second concern that I do not want in *all*, today. Other projects use "bundle" instead of "all" (like Apache CXF). I'll call it "bundle" from now now since it is not really "all". Let's review all of our modules, I mark with * what I see as minimal in "bundle": log4j-1.2-api log4j-api * log4j-bom log4j-core * log4j-distribution log4j-flume-ng * log4j-iostreams * log4j-jcl log4j-jmx-gui * log4j-jul log4j-liquibase * log4j-nosql * log4j-perf log4j-samples log4j-slf4j-impl log4j-taglib * log4j-to-slf4j log4j-web I'm not quite sure what "bom" does. I would NOT want log4j-1.2-api in bundle because I do not want to hijack the 1.2 API calls since I have code that provides custom 1.2 Appenders. Would including log4j-web cause problems for folks in a container? Would including any of the other logging modules cause issues like the one I have with 1.2 APIs? Gary On Thu, Dec 10, 2015 at 10:13 AM, Matt Sicker <[email protected]> wrote: > Most projects where I use log4j2, I include all the following dependencies > thanks to framework logging divergence: > > log4j-api > log4j-core > log4j-jcl > log4j-jul > log4j-slf4j-impl > log4j-1.2-api > > Shading these together would be super-convenient. Would anyone else be > interested in such a thing? I usually see this sort of thing in testing > frameworks (like mockito-all, hamcrest-all, etc.), but calling this > log4j-all would be incorrect. > > -- > Matt Sicker <[email protected]> > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
