summaryrefslogtreecommitdiffstats
path: root/slf4j-jcl/src
AgeCommit message (Collapse)AuthorFilesLines
2015-03-26Reformat all code with the exception of the slf4j-android module to use 4 ↵Ceki Gulcu6-689/+674
space indentation and max line width of 160.
2015-03-26Change Bundle-RequiredExecutionEnvironment declaration in MANIFEST.MF filesCeki Gulcu1-1/+1
Set the maven-compiler-plugin to target/source JDK 1.5 using a variable.
2014-12-14less warnings by EclipseCeki Gulcu1-2/+0
2013-09-12Fix BugZilla bug id 281Larry0ua1-3/+3
2013-03-25use a ConcurrentHashMap in various loger factories - fix bug #298Ceki Gulcu1-12/+12
2012-09-17improved javadocsCeki Gulcu1-1/+3
2012-09-06avoid version mismatch warning (when run with slf4j-api-1.6.jar) by setting ↵Ceki Gulcu1-1/+1
REQUESTED_VERSION to 1.6.99 instead of 1.7
2012-09-06adding vargs support to Logger interfaceCeki Gulcu2-16/+16
2011-10-16update license headers to current yearCeki Gulcu6-106/+94
2010-10-19Revert "make log4j-over-slf4j run in jboss 4.2"Ceki Gulcu1-1/+1
This reverts commit 3749a8521804cda6f22269923ad3ac5628e3a6cc.
2010-10-19make log4j-over-slf4j run in jboss 4.2Ceki Gulcu1-1/+1
2010-04-09Fixing bug 70Ceki Gulcu1-30/+32
2010-04-06As of SLF4J version 1.6.0, in the absence of an SLF4J binding,Ceki Gulcu2-6/+6
slf4j-api will default to a no-operation implementation discarding all log requests. Thus, instead of throwing an exception, SLF4J will emit a single warning message about the absence of a binding and proceed to discard all log requests without further protest.
2010-04-05- fixed bug 154Ceki Gulcu1-1/+1
- It is expected that all SLF4J releases in the 1.6.x and 2.0.x series will be mutually compatible. Note that the 2.0.x series is expected to require JDK 1.5 or later.
2010-02-25- preparing release 1.5.11Ceki Gulcu2-1/+20
- added code to detect the simultaneous presence of both log4j-over-slf4j.jar and slf4j-log4j12.jar. See also http://slf4j.org/codes.html#log4jDelegationLoop - added code to detect the simultaneous presence of both jcl-over-slf4j.jar and slf4j-jcl.jar. See also http://slf4j.org/codes.html#jclDelegationLoop - Fixed http://bugzilla.slf4j.org/show_bug.cgi?id=168
2009-12-03setting autocrlf = true on windows - no logical changesCeki Gulcu7-961/+961
2009-11-24Applied Hugues Malphettes's patch #65 as given in [1]Ceki Gulcu1-2/+2
[1] http://bugzilla.slf4j.org/show_bug.cgi?id=152
2009-11-23upped version to 1.5.10-SNAPSHOTCeki Gulcu1-1/+1
2009-10-28- Added missing "Export-Package" declaration for cal10n in the OSGiCeki Gulcu1-1/+1
manifest file for sfl4j-ext, fixing bug 156. - changed version number to 1.5.9.RC1. This fixes bug 157.
2009-09-23- started work on version 1.5.10Ceki Gulcu1-1/+1
- fixed bug 151 http://bugzilla.slf4j.org/show_bug.cgi?id=151
2009-09-04- Preparing release 1.5.9-RC0Ceki Gulcu1-1/+1
2009-07-20- start work on 1.5.9Ceki Gulcu1-1/+1
2009-06-11- fixed test scope issue in log4j-over-slf4jCeki Gulcu1-1/+1
- setting version number to 1.5.8 - updating news
2009-06-10next SLF4J version will be 2.0.0Ceki Gulcu1-1/+1
2009-01-23bumping version to 1.5.7-SNAPSHOTCeki Gulcu1-1/+1
2008-11-20An attempt at fixing bug 113 [1] and indirectly LBCORE-51 [2]. InsteadCeki Gulcu1-1/+10
of caching StaticLoggerBinder singleton, we retrieve afresh each time. This agrees well with native implementations with context selectors, e.g. logback. Unfortunately, the code in LoggerFactory is no longer dumb and totally obvious. [1] http://bugzilla.slf4j.org/show_bug.cgi?id=113 [2] http://jira.qos.ch/browse/LBCORE-51
2008-10-171.5.6-SNAPSHOT comes after 1.5.5Ceki Gulcu1-1/+1
In LoggerFactory.java we anticipate that 1.5.6 be 100% compatible with 1.5.5
2008-10-17Given the huge size of the SLF4J user base, we need a more lenient version Ceki Gulcu1-2/+3
check mechanism. For example, we can't expect external implementations such as Mina, jetty, jboss to follow SLF4J's release schedule. We just can't. This commit changes the version check policy to become elective. The FAQ includes an entry explaining the logic.
2008-10-16- preparing release 1.5.4Ceki Gulcu1-1/+1
2008-10-03- minor clean upCeki Gulcu1-3/+4
2008-10-02- keep tests quietCeki Gulcu1-0/+9
- fixed bug in version check code
2008-10-02- Adding version check support in each slf4j-binding Ceki Gulcu1-10/+18
Each copy of StaticLoggerBinder.java found in each binding now contains a field called VERSION. LoggerFactory checks that the version value found in the binding matches the expected version number as declared in LoggerFactory
2008-07-30- fix bug 71 by adding a readResolve method in all Logger implementations. The Ceki Gulcu1-5/+2
readResolve method returns the value computed by LoggerFactory.getLogger(name) where name is the serialized value of name for the current instance.
2008-02-26In response to bug report 73, adding "Fragment-Host: slf4j.api" line to Ceki Gulcu1-0/+1
every MANIFEST.MF file exporting org.slf4j.impl. See also http://bugzilla.slf4j.org/show_bug.cgi?id=73
2008-02-07- improvements to documentationCeki Gulcu1-26/+18
- minor license correction
2008-02-05- fixing bug #41 (http://bugzilla.slf4j.org/show_bug.cgi?id=41)Ceki Gulcu1-0/+1
by adding the following line to various MANIFEST.MF files Bundle-RequiredExecutionEnvironment: J2SE-1.3
2008-01-29- removed incorrect statement in javadocsCeki Gulcu1-6/+0
2007-08-20- removed slf4j-archetypeCeki Gulcu1-2/+2
- MANIFEST.MF files use ${project.version} as a variable in order to keep project version changes and the OSGI manifest in sync
2007-07-03improved testingCeki Gulcu1-0/+1
2007-07-03continued work on MDC supportCeki Gulcu2-0/+41
2007-05-03introducing the TRACE levelCeki Gulcu1-0/+98
2007-02-28Updated OSGi metadata to support version 1.3.1John E. Conlon1-2/+2
2007-02-24- Added versioning informationCeki Gulcu1-2/+2
- I did not remove the "Require-Bundle: slf4j.api" statement in MANIFEST.MF file of bindings. However, things seem to work even without it.
2007-02-22- Attempted to restore the state of the various MANIFEST.MF filesCeki Gulcu1-4/+3
where John E. Conlon left them previously. The project builds properly. I have yet to test/exercise the various OSGi modules. - Instead of manually editing the <Bundle-Version> element manually for each module, it is injected using the ${project_version_for_osgi} property as set in the parent pom.xml file.
2007-02-21Moving to older MANIFEST.MF styleCeki Gulcu1-0/+9
2007-02-21Moved the MarkerFactory to the slf4j-api moduleSebastien Pennec1-89/+0
2007-02-16Added the LoggerFactory class to the api module.Sebastien Pennec1-108/+0
A dummy StaticLoggerBinder class has also been added so that everything compiles nicely. The slf4j-api pom.xml file now uses an ant task to remove the dummy StaticLoggerBinder from the compiled classes so that each other module uses its own StaticLoggerBinder class.
2007-02-16Moved BasicMarker.java, BasicMarkerTest.java, BasicMarkerFactory.java, ↵Sebastien Pennec4-2/+5
MarkerIgnoringBase.java, MessageFormatter.java and Util.java to the org.slf4j.helpers package. Updated other modules classes accordingly
2007-02-06Replaced maven-jar-plugin with the org.apache.felix.maven-bundle-plugin for the John E. Conlon1-9/+0
creation of OSGi compatible jars. Changed multiproject version to 1.3.0-SNAPSHOT to adhere to maven and OSGi conventions. Packages from the sl4fj-api project are now copied at build time by the org.apache.felix.maven-bundle-plugin to all SLF4J Binding projects.
2006-12-28adding OSGI metadataCeki Gulcu1-0/+9