[slf4j-dev] [Bug 160] New: slf4j throw NullPointerException in singed applet

2009-11-25 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=160 Summary: slf4j throw NullPointerException in singed applet Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: critical Priority: P1

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-23 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #68 from Joern Huxhorn jo...@huxhorn.de 2009-11-23 19:59:25 --- (In reply to comment #65) Janos (boci.b...@gmail.com), Even if everyone on the planet was using JDK 1.7, SLF4J would still need to ensure binary compatibility with

[slf4j-dev] [Bug 152] Bundle manifest headers have invalid version specifications in SLF4J version 1 .5.9-RC0

2009-11-23 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=152 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[slf4j-dev] [Bug 159] Default to a behavior when no adapter found in the classpath

2009-11-21 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=159 --- Comment #1 from Ceki Gulcu lis...@qos.ch 2009-11-22 00:09:26 --- I started working this issue. Unfortunately, the required changes are more extensive than I had expected. I am going it to leave it as is for the time being. -- Configure

[slf4j-dev] [Bug 75] Cyclic dependency in OSGi

2009-11-17 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=75 Hugues Malphettes hmalphet...@intalio.com changed: What|Removed |Added Attachment #63 is|0 |1

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-16 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 Thorbjørn Ravn Andersen r...@runjva.com changed: What|Removed |Added CC||r...@runjva.com

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-16 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #63 from Thorbjørn Ravn Andersen r...@runjva.com 2009-11-16 09:26:55 --- (In reply to comment #61) Bug #133 is one such issue, something that I would have needed on several occasions, one of which was the bridging of XSLT messages

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-16 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #64 from boci boci.b...@gmail.com 2009-11-16 09:38:18 --- (In reply to comment #62) (In reply to comment #58) Disagree. Runtime compatibility is not required. Java 1.4 is dead. I think only bugfix release need for 1.4

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-16 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #67 from Thorbjørn Ravn Andersen r...@runjva.com 2009-11-16 19:56:00 --- (In reply to comment #64) Please be aware that slf4j serves many people with many different needs, and that Java is the new Cobol. Literally :) Some

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-14 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #54 from Ceki Gulcu lis...@qos.ch 2009-11-14 12:41:26 --- Any migration to from the current API to a new API must be transparent. Just keep in mind that for some users, having to install a binding, such as slf4j-jdk14.jar or

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-14 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #55 from Joern Huxhorn jo...@huxhorn.de 2009-11-14 17:45:22 --- No, no, no, nobody *has* to change their slf4j-imports, It's entirely optional. The original SLF4J-API would be left untouched. The same is the case for binding. They

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-14 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #56 from Ceki Gulcu lis...@qos.ch 2009-11-14 18:44:45 --- Sorry, I was not clear in my previous response. I had understood that the use of the new logger was optional which is the point of keeping the old one untouched. The issue is

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-14 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #58 from boci boci.b...@gmail.com 2009-11-14 20:08:06 --- (In reply to comment #56) Sorry, I was not clear in my previous response. I had understood that the use of the new logger was optional which is the point of keeping the old

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-14 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #60 from Mark A. Ziesemer b...@mark.ziesemer.com 2009-11-15 03:05:50 --- In response to comment #58 and comment #59: How is Runtime compatibility is not required a disagreement to comment #56, as stated? It seems that maybe everyone

[slf4j-dev] [Bug 148] Add support for Structured Data

2009-11-13 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=148 --- Comment #7 from Joern Huxhorn jo...@huxhorn.de 2009-11-13 11:24:01 --- This all sounds quite reasonable now. The only (small) inconsistency that could be an issue is the following line in your sample code in

[slf4j-dev] [Bug 148] Add support for Structured Data

2009-11-13 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=148 --- Comment #8 from Ralph Goers rgo...@apache.org 2009-11-13 15:46:58 --- There is little point in specifying logger.debug({}, data); the structured data object contains a message field so when structured data is present the normal message text

[slf4j-dev] [Bug 148] Add support for Structured Data

2009-11-11 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=148 --- Comment #6 from Ralph Goers rgo...@apache.org 2009-11-12 02:29:48 --- I've made the updates to make the Map unmodifiable and to expose the new methods. I still have a few changes to make to enforce the 32 character limitations. --

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #46 from boci boci.b...@gmail.com 2009-11-10 11:57:41 --- Nice, i hope the new slf4j released asap (which include these bugfix/feature). I don't understand why want fully backward (binary) compatible the next (2.0 or 5.0 ;) slf4j

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #47 from Joern Huxhorn jo...@huxhorn.de 2009-11-10 12:31:38 --- I guess this won't be included in the very near future ;) SLF4J 2.0 must stay compatible with 1.5.x because there can be only one version of SLF4J on the classpath and

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #48 from boci boci.b...@gmail.com 2009-11-10 12:46:19 --- (In reply to comment #47) I guess this won't be included in the very near future ;) SLF4J 2.0 must stay compatible with 1.5.x because there can be only one version of

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #49 from Joern Huxhorn jo...@huxhorn.de 2009-11-10 13:58:46 --- Alternatively, you could also give my implementation a try. The dependency is dependency groupIdde.huxhorn.lilith/groupId

[slf4j-dev] [Bug 148] Add support for Structured Data

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=148 --- Comment #3 from Joern Huxhorn jo...@huxhorn.de 2009-11-10 21:50:47 --- Concerning 1.): Ah, I think I understand. I guess that Hello ${Name} would reference Name in the StructuredData, right, and the actually logged message would be Hello

[slf4j-dev] [Bug 148] Add support for Structured Data

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=148 --- Comment #4 from Ralph Goers rgo...@apache.org 2009-11-10 22:35:19 --- Thanks. Yes, the placeholders work as you noted. That was actually an afterthought I had. It was pretty cool that Logback already had the code to do it. I had forgotten

[slf4j-dev] [Bug 148] Add support for Structured Data

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=148 --- Comment #5 from Ralph Goers rgo...@apache.org 2009-11-10 22:39:54 --- I should have also mentioned that it was necessary to add StructuredData to api instead of ext because Logback classic has no dependency on slfj-ext currently. Adding that

[slf4j-dev] [Bug 152] Bundle manifest headers have invalid version specifications in SLF4J version 1 .5.9-RC0

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=152 Hugues Malphettes hmalphet...@intalio.com changed: What|Removed |Added CC|

[slf4j-dev] [Bug 75] Cyclic dependency in OSGi

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=75 --- Comment #9 from Hugues Malphettes hmalphet...@intalio.com 2009-11-10 23:35:23 --- Created an attachment (id=63) -- (http://bugzilla.slf4j.org/attachment.cgi?id=63) patch to the slf4j.api pom to support logback-classic in osgi (equinox) Hi

[slf4j-dev] [Bug 152] Bundle manifest headers have invalid version specifications in SLF4J version 1 .5.9-RC0

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=152 --- Comment #2 from Eddy ecorb...@gmail.com 2009-11-10 23:40:45 --- Yes, this has been addressed by the fix for (duplicate?) bug #157 http://bugzilla.slf4j.org/show_bug.cgi?id=157 It is fixed in

[slf4j-dev] [Bug 152] Bundle manifest headers have invalid version specifications in SLF4J version 1 .5.9-RC0

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=152 --- Comment #3 from Hugues Malphettes hmalphet...@intalio.com 2009-11-10 23:50:40 --- In a similar situation I used http://mojo.codehaus.org/build-helper-maven-plugin/parse-version-mojo.html 1- invoke it (in the parent pom to not copy-paste it

[slf4j-dev] [Bug 152] Bundle manifest headers have invalid version specifications in SLF4J version 1 .5.9-RC0

2009-11-10 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=152 --- Comment #4 from Hugues Malphettes hmalphet...@intalio.com 2009-11-11 00:40:34 --- Created an attachment (id=64) -- (http://bugzilla.slf4j.org/attachment.cgi?id=64) generate osgi compliant Bundle-Version when version ends with -SNAPSHOT It

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-09 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 boci boci.b...@gmail.com changed: What|Removed |Added CC||boci.b...@gmail.com --- Comment

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-11-09 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #44 from boci boci.b...@gmail.com 2009-11-09 14:02:45 --- (In reply to comment #43) (In reply to comment #40) The problem is not in the implementation but the change in the org.slf4j.Logger interface. Adding methods to an

[slf4j-dev] [Bug 157] slf4j-* uses invalid OSGi version in bundle headers

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=157 --- Comment #4 from Pete Muir pm...@redhat.com 2009-10-29 11:21:48 --- Roger Kitain confirmed this fix works. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are

[slf4j-dev] [Bug 158] New: Placeholder resolution for logger method varargs

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=158 Summary: Placeholder resolution for logger method varargs Product: SLF4J Version: 1.5.x Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P1

[slf4j-dev] [Bug 158] Placeholder resolution for logger method varargs

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=158 --- Comment #1 from Ceki Gulcu lis...@qos.ch 2009-10-29 12:32:03 --- Hello Marci, Try the following syntax: logger.debug(Bla bla {}, new Object[] {stringArray}); -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email

[slf4j-dev] [Bug 158] Placeholder resolution for logger method varargs

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=158 --- Comment #2 from Marco Behler m...@bwso.de 2009-10-29 13:21:57 --- (In reply to comment #1) Hello Marci, Try the following syntax: logger.debug(Bla bla {}, new Object[] {stringArray}); Hi Ceki, this works almost as expected. Just a

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 --- Comment #2 from Pete Muir pm...@redhat.com 2009-10-29 13:34:00 --- Created an attachment (id=62) -- (http://bugzilla.slf4j.org/attachment.cgi?id=62) Fix exports, add import on cal10n, use property in POM I believe that slf4j-ext should be

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 Pete Muir pm...@redhat.com changed: What|Removed |Added Attachment #62|Fix exports, add import on |Add export on org.slf4j.ext

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 --- Comment #4 from Ceki Gulcu lis...@qos.ch 2009-10-29 14:55:39 --- Patch applied [1]. The export and import clauses now actually makes sense. Sorry about the 0.7 version declaration instead of ${cal10n.version}. [1]

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 --- Comment #5 from Pete Muir pm...@redhat.com 2009-10-29 15:00:42 --- The applied patch appears to be missing the export org.slf4j.ext;version=${project.version} which allows people to use XLogger Here is a patch. diff --git

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 --- Comment #6 from Ceki Gulcu lis...@qos.ch 2009-10-29 15:10:58 --- applied -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 --- Comment #7 from Ceki Gulcu lis...@qos.ch 2009-10-29 15:15:55 --- removed cruft. should be fine now: http://git.qos.ch/gitweb/?p=slf4j.git;a=commit;h=58e6b11530ab61312326b4d5f4bf43900797d650 -- Configure bugmail:

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 --- Comment #8 from Pete Muir pm...@redhat.com 2009-10-29 19:21:57 --- Roger Kitain has verified these fixes in GlassFish. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email --- You are receiving this mail because:

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 --- Comment #9 from Ceki Gulcu lis...@qos.ch 2009-10-29 19:24:31 --- Does this mean we are go for a public release of 1.5.9RC1 and cal10n 0.7.2? -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email --- You are receiving

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 --- Comment #10 from Pete Muir pm...@redhat.com 2009-10-29 19:25:39 --- Yes, we have verified slf4j 156 and 157 and CAL-8 and CAL-9 are all fixed. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email --- You are

[slf4j-dev] [Bug 158] Placeholder resolution for logger method varargs

2009-10-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=158 Joern Huxhorn jo...@huxhorn.de changed: What|Removed |Added CC||jo...@huxhorn.de ---

[slf4j-dev] [Bug 156] New: slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-28 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 Summary: slf4j-ext OSGi bundle headers need updating for cal10n support Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Mac OS X 10.3 Status: NEW

[slf4j-dev] [Bug 157] New: slf4j-* uses invalid OSGi version in bundle headers

2009-10-28 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=157 Summary: slf4j-* uses invalid OSGi version in bundle headers Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Mac OS X 10.3 Status: NEW Severity: blocker

[slf4j-dev] [Bug 157] slf4j-* uses invalid OSGi version in bundle headers

2009-10-28 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=157 Ralph Goers rgo...@apache.org changed: What|Removed |Added CC||rgo...@apache.org ---

[slf4j-dev] [Bug 157] slf4j-* uses invalid OSGi version in bundle headers

2009-10-28 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=157 --- Comment #2 from Pete Muir pm...@redhat.com 2009-10-28 17:33:13 --- In the interest of user-friendliness, and promoting community testing of release candidates, I would argue that they should be usable in all places the release is. But this is

[slf4j-dev] [Bug 157] slf4j-* uses invalid OSGi version in bundle headers

2009-10-28 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=157 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[slf4j-dev] [Bug 156] slf4j-ext OSGi bundle headers need updating for cal10n support

2009-10-28 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=156 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[slf4j-dev] [Bug 138] Class path contains multiple SLF4J bindings

2009-10-27 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=138 Joern Huxhorn jo...@huxhorn.de changed: What|Removed |Added CC||jo...@huxhorn.de ---

[slf4j-dev] [Bug 155] New: Manage Multiple SLF4J-Implementations

2009-10-24 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=155 Summary: Manage Multiple SLF4J-Implementations Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: enhancement Priority: P1

[slf4j-dev] [Bug 154] New: slf4j-api reports an incompatibility problem

2009-10-22 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=154 Summary: slf4j-api reports an incompatibility problem Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: blocker Priority: P1

[slf4j-dev] [Bug 153] NPE in SLF4JLocationAwareLog during application shutdown

2009-10-20 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=153 --- Comment #2 from akuhtz andreas.ku...@siemens.com 2009-10-20 19:15:18 --- This is the stacktrace that I can see in the logfile. Unfortunately I cannot provide a testcase as I see this only during shutdown of a appserver instance ;-(

[slf4j-dev] [Bug 121] ClassNotFoundException exception in Eclipse/RCP unit tests

2009-10-13 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=121 Eddy ecorb...@gmail.com changed: What|Removed |Added CC||ecorb...@gmail.com --

[slf4j-dev] [Bug 152] New: Bundle manifest headers have invalid version specifications in SLF4J version 1 .5.9-RC0

2009-10-12 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=152 Summary: Bundle manifest headers have invalid version specifications in SLF4J version 1.5.9-RC0 Product: SLF4J Version: 1.5.x Platform: All OS/Version: All Status: NEW

[slf4j-dev] [Bug 150] LogManager is needed but not implemented yet

2009-10-09 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=150 Rick Beton rick.be...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED

[slf4j-dev] [Bug 138] Class path contains multiple SLF4J bindings

2009-09-30 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=138 --- Comment #8 from Matthew Teeter mrm...@gmail.com 2009-09-30 20:31:40 --- I've encountered this same issue on Weblogic 9.1, 9.2, and 10.0, which does not happen on Tomcat. I've filed a bug with Oracle on 9/2/2009 and they are looking into it.

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-09-28 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 Nicolas Lalevée nicolas.lale...@hibnet.org changed: What|Removed |Added CC|

[slf4j-dev] [Bug 70] logging a stack trace along with a parameterized string solution proposal

2009-09-28 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=70 Nicolas Lalevée nicolas.lale...@hibnet.org changed: What|Removed |Added CC|

[slf4j-dev] [Bug 151] jcl104-over-slf4j should not be producing a jar file

2009-09-23 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=151 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from

[slf4j-dev] [Bug 151] jcl104-over-slf4j should not be producing a jar file

2009-09-23 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=151 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added CC||lis...@qos.ch

[slf4j-dev] [Bug 150] LogManager is needed but not implemented yet

2009-09-23 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=150 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[slf4j-dev] [Bug 151] New: jcl104-over-slf4j should not be producing a jar file

2009-09-22 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=151 Summary: jcl104-over-slf4j should not be producing a jar file Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Mac OS X 10.3 Status: NEW Severity: minor Priority:

[slf4j-dev] [Bug 110] Create a bridge between System.out/System.err and SLF4J

2009-09-21 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=110 Stephen Duncan Jr stephen.dun...@gmail.com changed: What|Removed |Added CC|

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-09-17 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #42 from Ralph Goers rgo...@apache.org 2009-09-17 08:15:53 --- I have added support for varargs to LoggerWrapper on my fork at git://github.com/rgoers/slf4j.git. This also contains changes in support of bugs 127 and 148. To take

[slf4j-dev] [Bug 150] New: LogManager is needed but not implemented yet

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=150 Summary: LogManager is needed but not implemented yet Product: SLF4J Version: 1.5.x Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 Rick Beton rick.be...@gmail.com changed: What|Removed |Added CC||rick.be...@gmail.com ---

[slf4j-dev] [Bug 150] LogManager is needed but not implemented yet

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=150 Thorbjørn Ravn Andersen thorbjo...@gmail.com changed: What|Removed |Added CC|

[slf4j-dev] [Bug 150] LogManager is needed but not implemented yet

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=150 --- Comment #2 from Ceki Gulcu lis...@qos.ch 2009-09-15 17:36:04 --- As Thorbjørn points out, it would be helpful if you could list the missing methods in LogManager. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 Thorbjørn Ravn Andersen thorbjo...@gmail.com changed: What|Removed |Added CC|

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #37 from Mark A. Ziesemer b...@mark.ziesemer.com 2009-09-15 18:28:27 --- In response to comment #36, please don't add any additional arbitrary limits. Is 10 any better than 2? Why not 20? I don't have the source code in front of

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #39 from Thorbjørn Ravn Andersen thorbjo...@gmail.com 2009-09-15 20:56:32 --- I was just thinking that info(... Object o1, Object o2, Object o3) could be implemented in slf4j itself by just calling info( ... new Object[] {o1,

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #40 from Ceki Gulcu lis...@qos.ch 2009-09-15 21:29:50 --- The problem is not in the implementation but the change in the org.slf4j.Logger interface. Adding methods to an interface is not backward compatible... -- Configure bugmail:

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #41 from Thorbjørn Ravn Andersen thorbjo...@gmail.com 2009-09-15 21:53:11 --- Ah, forgot that Logger is an interface and not a class. Bummer. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email --- You are

[slf4j-dev] [Bug 138] Class path contains multiple SLF4J bindings

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=138 --- Comment #6 from Łukasz Rżanek lukasz.rza...@gmail.com 2009-09-15 23:54:54 --- Created an attachment (id=61) -- (http://bugzilla.slf4j.org/attachment.cgi?id=61) Proposed solution? The solution proposed in the discussion linked above

[slf4j-dev] [Bug 138] Class path contains multiple SLF4J bindings

2009-09-15 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=138 Robert Elliot rob...@teviotia.co.uk changed: What|Removed |Added CC||rob...@teviotia.co.uk

[slf4j-dev] [Bug 149] Typo in version mismatch warning message documentation

2009-09-13 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=149 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added CC||lis...@qos.ch

[slf4j-dev] [Bug 149] New: Typo in version mismatch warning message documentation

2009-09-09 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=149 Summary: Typo in version mismatch warning message documentation Product: SLF4J Version: 1.5.x Platform: All URL: http://www.slf4j.org/codes.html#version_mismatch OS/Version: All

[slf4j-dev] [Bug 127] LocationAwareLogger does not have a method that accepts the argument array

2009-09-07 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=127 --- Comment #3 from Ralph Goers rgo...@apache.org 2009-09-07 09:11:41 --- I have created the fix for this at git://github.com/rgoers/slf4j.git. It also includes support for StructuredData to support the new IETF Syslog format. -- Configure

[slf4j-dev] [Bug 148] New: Add support for Structured Data

2009-09-07 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=148 Summary: Add support for Structured Data Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Mac OS X 10.3 Status: NEW Severity: enhancement Priority: P1

[slf4j-dev] [Bug 147] New: Document the fact an LogLogger is a Logger

2009-09-05 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=147 Summary: Document the fact an LogLogger is a Logger Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P1

[slf4j-dev] [Bug 147] Document the fact an LogLogger is a Logger

2009-09-05 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=147 --- Comment #1 from Ceki Gulcu lis...@qos.ch 2009-09-05 14:58:23 --- Two bits of information should answer your question. 1) A LocLogger *is* a Logger and can be used as such. 2) When you write Logger lx = LoggerFactory.getLogger(X);

[slf4j-dev] [Bug 117] log4j-over-slf4j has no OSGi bundle manifest

2009-09-04 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=117 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[slf4j-dev] [Bug 117] log4j-over-slf4j has no OSGi bundle manifest

2009-09-02 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=117 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added CC|lis...@qos.ch | Status|NEW

[slf4j-dev] [Bug 146] New: NullPointerException when getILoggerFactory()

2009-09-01 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=146 Summary: NullPointerException when getILoggerFactory() Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: blocker Priority: P1

[slf4j-dev] [Bug 127] LocationAwareLogger does not have a method that accepts the argument array

2009-09-01 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=127 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #2 from

[slf4j-dev] [Bug 143] Include licensing information in pom.xml

2009-08-24 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=143 Ceki Gulcu li...@slf4j.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-08-23 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 Thomas Timbul tho...@gtsquare.com changed: What|Removed |Added CC||tho...@gtsquare.com --

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-08-19 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added CC|lis...@qos.ch | -- Configure bugmail:

[slf4j-dev] [Bug 145] New: Typos in http://slf4j.org/legacy.html

2009-08-19 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=145 Summary: Typos in http://slf4j.org/legacy.html Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: minor Priority: P1

[slf4j-dev] [Bug 145] Typos in http://slf4j.org/legacy.html

2009-08-19 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=145 --- Comment #1 from Ceki Gulcu lis...@qos.ch 2009-08-19 11:26:21 --- If both are present *simulatenously* , slf4j calls will be delegated to log4j, and log4j calls redirected to SLF4j, resulting in an endless recursion. simulatenously is a typo

[slf4j-dev] [Bug 31] Varargs for Logger methods

2009-08-18 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=31 David Rosenstrauch dar...@darose.net changed: What|Removed |Added CC||dar...@darose.net

[slf4j-dev] [Bug 144] New: Logger Interface Should (Arguably) Extend Serializable

2009-08-09 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=144 Summary: Logger Interface Should (Arguably) Extend Serializable Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: minor Priority:

[slf4j-dev] [Bug 143] Include licensing information in pom.xml

2009-07-30 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=143 --- Comment #3 from Ceki Gulcu lis...@qos.ch 2009-07-30 11:19:51 --- How is the contents of licences tag in pom.xml useful? Is it because it provides a well-known and convenient place for licensing information or is there another use? --

[slf4j-dev] [Bug 143] Include licensing information in pom.xml

2009-07-30 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=143 Joern Huxhorn jo...@huxhorn.de changed: What|Removed |Added CC||jo...@huxhorn.de ---

[slf4j-dev] [Bug 143] Include licensing information in pom.xml

2009-07-30 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=143 --- Comment #5 from Joern Huxhorn jo...@huxhorn.de 2009-07-30 16:37:13 --- (In reply to comment #4) The licenses are inherited from the parent. They are useful to visualize the licenses of all dependencies of a project. See

[slf4j-dev] [Bug 142] NPE when logging with SLF4JLocationAwareLog after Serialization

2009-07-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=142 Ceki Gulcu lis...@qos.ch changed: What|Removed |Added Status|NEW |ASSIGNED -- Configure

[slf4j-dev] [Bug 142] NPE when logging with SLF4JLocationAwareLog after Serialization

2009-07-29 Thread bugzilla-daemon
http://bugzilla.slf4j.org/show_bug.cgi?id=142 --- Comment #1 from Ceki Gulcu lis...@qos.ch 2009-07-29 11:41:15 --- Hello Mark, Thank you for this report. I just started studying the problem. Which version of slf4j-api and jcl-over-slf4j are you using? Which slf4j binding? -- Configure

  1   2   3   4   5   6   >