Well, actually if you don't have any "real" implementation the API has something equivalent to the simple logger in Commons Logging. It isn't too useful. Core provides the "real" Log4j 2 implementation. User's code against the classes in the API jar but also need the core jar to run. The "combined" jar replaces both of those.
Ralph On Nov 1, 2012, at 7:28 AM, Paul Benedict wrote: > Correct me if wrong, but doesn't "core" provide the default logging > implementation? > > On Thu, Nov 1, 2012 at 9:07 AM, Ralph Goers <rgo...@apache.org> wrote: > OK. The current combined jar only includes API and core and has no required > dependencies that are different than core. I am imagining that many will > prefer to use this single jar instead of having to include both the API and > core jars. What is your opinion on that and if positive, what would you name > it? > > Ralph > > On Nov 1, 2012, at 6:51 AM, Paul Benedict <pbened...@apache.org> wrote: > >> I may have misunderstood, but I'll give it another shot! >> >> I don't like combined jars. It's because there's too many dependencies >> associated with them. It makes the POM kind of worthless because any >> extensions are all <optional>true</option> ... so you have to go manually >> add those to your Maven project anyway to get them. I think that kind of >> defeats the purpose of an all-in-one jar. >> >> My only point was if there is a combined jar that has everything, call it >> "-all" not "-combined" >> >> Paul >> >> >> On Thu, Nov 1, 2012 at 7:19 AM, Tushar Kapila <tgkp...@gmail.com> wrote: >> I prefer all.jar or ApiAndCore.jar >> Even if OSes accept special characters there will always be closed systems >> that do not. Exampple hyphen is okay in a domain name but one of the visa >> test pit's don't like them >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >> >> >