Hi,
On 2/16/07, Eric Crahen <[EMAIL PROTECTED]> wrote:
> As I said, deploying the correct implementation jar IS a kind of
> configuration, weather you call it that or not.
Exactly, and I think this should be the *only* configuration SLF4J
would ever need. Any solution that requires extra configur
I'm fine with it just picking the first one, but certainly when there is
more than one a very, very clear error message should be output that tells a
user exactly what is wrong and what to do.
On 2/16/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 2/16/07, Eric Crahen <[EMAIL PROTECTED]>
Hi,
On 2/16/07, Eric Crahen <[EMAIL PROTECTED]> wrote:
> I'm fine with it just picking the first one, but certainly when there is
> more than one a very, very clear error message should be output that tells a
> user exactly what is wrong and what to do.
I've seen a couple of legitimate cases wher
On 2/16/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Exactly, and I think this should be the *only* configuration SLF4J
would ever need. Any solution that requires extra configuration
properties or explicit precedence settings is IMHO too much.
The fact that SLF4J always uses the implementation
Hi,
On 2/16/07, Eric Crahen <[EMAIL PROTECTED]> wrote:
> You don't need to get as complicated as doing precedence, but I still think
> that including the stderr logger as the fallback and default is the way to go.
Sounds OK to me.
> Those couple of legitimate cases you mentioned are valid (logba
Author: seb
Date: Fri Feb 16 15:50:08 2007
New Revision: 723
Added:
slf4j/trunk/slf4j-api/src/main/java/org/slf4j/helpers/
slf4j/trunk/slf4j-api/src/main/java/org/slf4j/helpers/BasicMarker.java
- copied, changed from r722,
/slf4j/trunk/slf4j-api/src/main/java/org/slf4j/impl/BasicMarke
Author: seb
Date: Fri Feb 16 15:57:48 2007
New Revision: 724
Removed:
slf4j/trunk/slf4j-api/src/main/java/org/slf4j/impl/
slf4j/trunk/slf4j-api/src/test/java/org/slf4j/impl/
Log:
deleted unused packages
___
dev mailing list
dev@slf4j.org
http://ww
Author: seb
Date: Fri Feb 16 18:49:52 2007
New Revision: 725
Modified:
slf4j/trunk/slf4j-api/pom.xml
Log:
reformat
Modified: slf4j/trunk/slf4j-api/pom.xml
==
--- slf4j/trunk/slf4j-api/pom.xml (original)
+++ slf4
Author: seb
Date: Fri Feb 16 19:27:16 2007
New Revision: 726
Added:
slf4j/trunk/slf4j-api/src/main/java/org/slf4j/LoggerFactory.java
slf4j/trunk/slf4j-api/src/main/java/org/slf4j/impl/
slf4j/trunk/slf4j-api/src/main/java/org/slf4j/impl/StaticLoggerBinder.java
Removed:
slf4j/trunk/slf4j
Hello all,
I've just committed some changes about the LoggerFactory class.
Now, the api module contains the LoggerFactory class, it is not present in the
other
modules anymore. It also contains a dummy StaticLoggerBinder implementation to
make
sure it compiles nicely.
This dummy class is rem
Great.
I think we should now move forward with replacing that with the Service API.
On 2/16/07, Sebastien Pennec <[EMAIL PROTECTED]> wrote:
Hello all,
I've just committed some changes about the LoggerFactory class.
Now, the api module contains the LoggerFactory class, it is not present in
th
Hello,
I've had some issues today by building the jcl-over-slf4j module. I get this
error:
[INFO] [bundle:bundle]
[ERROR] Unresolved references to [org.slf4j.spi] by class(es) on the
Bundle-Classpath[Jar:dot]:
[org/apache/commons/logging/impl/SLF4FLogFactory.class,
org/apache/commons/logging/
Hi Sebastien,
I am seeing OSGi testing problems that seem to be related to the 723
revision.
After revision 723 - OSGi bindings tests are failing with
java.lang.NoClassDefFoundError: org/slf4j/helpers/MarkerIgnoringBase.
Reason: Latest 723 revisions introduce a new package org.slf4j.helpers
p
Hi Sebastien,
Yes your guess is correct. I'm investigating. See also issue related
to your last release.
John
Sebastien Pennec wrote:
> Hello,
>
> I've had some issues today by building the jcl-over-slf4j module. I get this
> error:
>
> [INFO] [bundle:bundle]
> [ERROR] Unresolved references
At 07:32 PM 2/16/2007, Sebastien Pennec wrote:
>Hello all,
>
>I've just committed some changes about the LoggerFactory class.
>
>Now, the api module contains the LoggerFactory class, it is not present in
>the other
>modules anymore. It also contains a dummy StaticLoggerBinder
>implementation to m
Hi Sebastien,
I see what is going on, but don't know what to do about it.
The build problem is related to the introduction of a new package
dependency to
the artifact (jar/bundle) created by jcl-over-slf4j. This change
happened at revision 722.
The new package dependency is
org.slf4j.spi
an
Author: jconlon
Date: Fri Feb 16 21:42:47 2007
New Revision: 727
Modified:
slf4j/trunk/slf4j-jcl/pom.xml
Log:
Added the new org.slf4j.helpers as a private package to the bundle.
Modified: slf4j/trunk/slf4j-jcl/pom.xml
===
Author: jconlon
Date: Fri Feb 16 21:43:52 2007
New Revision: 728
Modified:
slf4j/trunk/slf4j-jdk14/pom.xml
Log:
Added the new org.slf4j.helpers as a private package to the bundle.
Modified: slf4j/trunk/slf4j-jdk14/pom.xml
===
show_bug.cgi?id=23
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution||FIXED
-
Author: jconlon
Date: Fri Feb 16 21:47:32 2007
New Revision: 729
Modified:
slf4j/trunk/slf4j-log4j12/pom.xml
Log:
Added the new org.slf4j.helpers as a private package to the bundle.
Modified: slf4j/trunk/slf4j-log4j12/pom.xml
===
Author: jconlon
Date: Fri Feb 16 21:48:13 2007
New Revision: 730
Modified:
slf4j/trunk/slf4j-nop/pom.xml
Log:
Added the new org.slf4j.helpers as a private package to the bundle.
Modified: slf4j/trunk/slf4j-nop/pom.xml
===
Author: jconlon
Date: Fri Feb 16 21:48:36 2007
New Revision: 731
Modified:
slf4j/trunk/slf4j-simple/pom.xml
Log:
Added the new org.slf4j.helpers as a private package to the bundle.
Modified: slf4j/trunk/slf4j-simple/pom.xml
=
I believe it was my bad. I introduced a new dependency without
thinking about the consequences at the OSGi level. My apologies for
the inconvenience.
There are two possible solutions:
1) move the LocationAwareLogger interface from org.slf4j.spi to org.slf4j.
2) export the org.slf4j.spi package
Author: jconlon
Date: Fri Feb 16 22:03:05 2007
New Revision: 732
Modified:
slf4j/trunk/pom.xml
Log:
Added profile for building and testing OSGi projects.
Modified: slf4j/trunk/pom.xml
==
--- slf4j/trunk/pom.xml (origi
Author: ceki
Date: Fri Feb 16 22:50:32 2007
New Revision: 733
Modified:
slf4j/trunk/slf4j-site/src/site/resources/news.html
Log:
updates news
Modified: slf4j/trunk/slf4j-site/src/site/resources/news.html
==
--- slf
Your right, neither do I want to increase the number of classes in the
org.slf4j packages. But we are basically doing the same kind of thing
with the second approach as well - exposing our selves to greater
coupling by clients. By exporting the org.slf4j.spi package we are
exporting what was
Sorry I meant to say 1.3.0-SNAPSHOT instead of 1.5.0.
John E. Conlon wrote:
> Your right, neither do I want to increase the number of classes in the
> org.slf4j packages. But we are basically doing the same kind of thing
> with the second approach as well - exposing our selves to greater
> cou
27 matches
Mail list logo
