Content deleted Content added
mNo edit summary |
→categories, popularity and commons logging: Added a remark |
||
Line 16:
I see a citation is demanded for assessing popularity. The [[Apache Maven]] repositories can be used to determine dependencies on commons-logging, log4j and others, such as this listing of log4j's use: [[http://mvnrepository.com/artifact/log4j/log4j/1.2.13]]. However, detecting use of the java logging API would need introspection on the libraries in the repository itself. It could be possible to do this and write a paper on the subject, one wikipedia could cite. Note that as commons-logging is not a logger so much as an [[Extra Layer of Indirection]]; if commons-logging+log4j are found together, it means log4j is used via commons-logging APIs. [[User:SteveLoughran|SteveLoughran]] ([[User talk:SteveLoughran|talk]])
== categories, popularity and commons logging ==
AFAIK this article should describe
Logging Frameworks (log4j, Java SDK Logger, Logback) and Logging Wrappers (Commons Logging and SLF4J) and clearly separate them.
Logging Frameworks simplyfi application development by eliminating the popular System.out() usage with a meaningfull API and a configurable and extendable backend to output the Log entries to the console, files or even databases.
Logging Wrapper help application and library developers to provide logging independant from the chosen logging framework.
It would also help to at least mention the discussion around commons logging and classloaders, like this reference:
Spring Framework reference 3.0 Chapter 1.3.2.1 Not using commons logging
"Unfortunately, the runtime discovery algorithm in commons-logging, while convenient for the end-user, is problematic. If we could turn back the clock and start Spring now as a new project it would use a different logging dependency." [[http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/overview.html]]
| |||