Jump to content

Talk:Java logging framework

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by ZooFari (talk | contribs) at 04:03, 11 November 2009 (Adding WikiProject Java assessment per request (Mistake?) using AWB). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconJava Unassessed
WikiProject iconThis article is within the scope of WikiProject Java, a collaborative effort to improve the coverage of Java on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
???This article has not yet received a rating on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.

The summary paragraphs on log4j and Java Logging make it appear that log4j should be used just because it is more popular, but log4j is more popular because it has been in existence longer. Rewriting these two paragraphs would improve the neutrality. LanceHelsten (talk) 18:21, 28 November 2007 (UTC)[reply]

I could do a when/where, but it would be opinion.
  • Log4J: works on older Java versions (not so relevant), really good loggers, good configuration by in-classpath files and API.
  • Commons-Logging. Not a real logger, just a wrapper around 3 logging APIs, one of which (avalon logkit) is obsolete and never encountered in the wild. By adopting commons-logging in a library, you give whoever uses the app their own choice of what to use behind it.
  • Java Logging API. built in to the JVM. Hard to configure -external files only. Not easily changed on the fly. No useful output formats.
  • SL4J. Switch logging by using different libraries.
  • printing to standard output channels directly. Useful when logging hasn't even been bootstrapped yet. SteveLoughran (talk) 13:06, 6 March 2008 (UTC)[reply]

measuring popularity

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: [[1]]. 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. SteveLoughran (talk)