Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
On 19 May 2004, at 10:18, Ceki Gülcü wrote: This time in English: Experiments I conducted also show that while it is fairly easy to modify commons-logging to make it compile-time compatible with both log4j 1.2 and 1.3alpha, there will be problems at runtime. In fact, commons-logging source compiled with log4j-1.2.x.jar will only run with log4j-1.2.x.jar but not log4j-1.3alpha.jar. Similarly, the *same* commons-logging source code will compile fine with log4j-1.3alpha.jar but it will only run with log4j-1.3alpha.jar, not log4j-1.2.x.jar. In summary, the changes proposed by Mario Ivankovits and myself achieve compile-time compatibility but not run-time compatibility. good that's what i'd expected :) sorry if we had our wires crossed before: i'm more used to talking about binary compatibility and compile compatibility where you talk about run-time compatibility and compile-time compatibility (respectively). - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
Still no news on this item? On 2004-05-13 17:20:38 Adam R. B. Jack wrote: From: Mario Ivankovits [EMAIL PROTECTED] wrote: Just for the records - i already posted a patch, maybe a logging-committer might pick it up http://issues.apache.org/bugzilla/show_bug.cgi?id=28933 Excellent, thank you. I really hope one of the commons logging folks will get to it today, and we can have a fuller Gump tonight. There is some good activity on projects infrequently Gumped, and I'd like to see that momentum continue. regards, Adam -- Ceki Gülcü For log4j documentation consider The complete log4j manual ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
i am more than a little confused about this whole issue. i've taken a look in cvs and priority still seems to be in existence (and undeprecated). when i looked at the gump record for sunday, common-logging seems to have passed. can someone please either explain where the log4j changes are and when the failure occurred? (as for the suggested patch) i'd be very unhappy about committing a patch which broke backwards compatibility with the most common versions of log4j (especially this close to a release). in fact, i'd probably think about vetoing any such change. there are a number of important upcoming releases who would be directly effected by these changes as well as a very large number of users of these releases who would be forced to upgrade. probably the right solution would be to create three different log implementations each targeted at a major log4j version and use some sort of reflection to work out which to use. this isn't very difficult to do but i'm not sure how gump would handle this, though. any ideas about gump-friendly build strategies for this? - robert On 17 May 2004, at 17:05, Ceki Gülcü wrote: Still no news on this item? On 2004-05-13 17:20:38 Adam R. B. Jack wrote: From: Mario Ivankovits [EMAIL PROTECTED] wrote: Just for the records - i already posted a patch, maybe a logging-committer might pick it up http://issues.apache.org/bugzilla/show_bug.cgi?id=28933 Excellent, thank you. I really hope one of the commons logging folks will get to it today, and we can have a fuller Gump tonight. There is some good activity on projects infrequently Gumped, and I'd like to see that momentum continue. regards, Adam -- Ceki Gülcü For log4j documentation consider The complete log4j manual ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
I know logger know this better than I, but in case quick answer help w/ timezones... i am more than a little confused about this whole issue. i've taken a look in cvs and priority still seems to be in existence (and undeprecated). when i looked at the gump record for sunday, common-logging seems to have passed. can someone please either explain where the log4j changes are and when the failure occurred? The issues isn't wether Priority exists, so much as the called method. It now take Level only, the Priority version of the method has been removed. [BTW: This has (I am told) been deprecated for 2 years, so this really is somewhat overdue.) BTW: Whilst waiting for C-L to address this problem I let Gump build C-L on log4j 1.2, temporarily. That is no longer the case, you'll see failures in future Gump outputs (w/o a change). (as for the suggested patch) i'd be very unhappy about committing a patch which broke backwards compatibility with the most common versions of log4j (especially this close to a release). in fact, i'd probably think about vetoing any such change. there are a number of important upcoming releases who would be directly effected by these changes as well as a very large number of users of these releases who would be forced to upgrade. I beleive that it won't break compatibility any log4j within the last 2 years, because the alternate method has been there. If true, is that acceptable enough? Change has to be allow to occur, and this seems as smooth a transition as possible. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
robert burrell donkin wrote: i am more than a little confused about this whole issue. i've taken a look in cvs and priority still seems to be in existence (and undeprecated). when i looked at the gump record for sunday, common-logging seems to have passed. can someone please either explain where the log4j changes are and when the failure occurred? (as for the suggested patch) i'd be very unhappy about committing a patch which broke backwards compatibility with the most common versions of log4j (especially this close to a release). in fact, i'd probably think about vetoing any such change. there are a number of important upcoming releases who would be directly effected by these changes as well as a very large number of users of these releases who would be forced to upgrade. Ceki Gülcü wrote: Fortunately, the required changes are easy and are backward compatible. Commons-logging code needs to be changed as follows. The change was in the Category class, formerly the log methods accepted a priority but this has change to a level now. But it looks like the change isnt really backward compatible, i have tried this now and got the following exception (patched commons-logging and log4j-1.2.8): java.lang.NoSuchMethodError: org.apache.log4j.Logger.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V at org.apache.commons.logging.impl.Log4JLogger.fatal(Log4JLogger.java:161) at org.apache.commons.vfs.test.RunTest.main(RunTest.java:31) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.intellij.rt.execution.application.AppMain.main(Unknown Source) Maybe we relly need a new Log4J implementation depending on its version this is bad, isnt it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
I'm no expert on when to [or not to] cross post, but this looks like a good topic for discussion in these two places at once. regards Adam - Original Message - From: Mario Ivankovits [EMAIL PROTECTED] To: Jakarta Commons Developers List [EMAIL PROTECTED] Sent: Monday, May 17, 2004 2:33 PM Subject: Re: [EMAIL PROTECTED]: jakarta-commons/commons-logging failed robert burrell donkin wrote: i am more than a little confused about this whole issue. i've taken a look in cvs and priority still seems to be in existence (and undeprecated). when i looked at the gump record for sunday, common-logging seems to have passed. can someone please either explain where the log4j changes are and when the failure occurred? (as for the suggested patch) i'd be very unhappy about committing a patch which broke backwards compatibility with the most common versions of log4j (especially this close to a release). in fact, i'd probably think about vetoing any such change. there are a number of important upcoming releases who would be directly effected by these changes as well as a very large number of users of these releases who would be forced to upgrade. Ceki Gülcü wrote: Fortunately, the required changes are easy and are backward compatible. Commons-logging code needs to be changed as follows. The change was in the Category class, formerly the log methods accepted a priority but this has change to a level now. But it looks like the change isnt really backward compatible, i have tried this now and got the following exception (patched commons-logging and log4j-1.2.8): java.lang.NoSuchMethodError: org.apache.log4j.Logger.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/ lang/Object;Ljava/lang/Throwable;)V at org.apache.commons.logging.impl.Log4JLogger.fatal(Log4JLogger.java:161) at org.apache.commons.vfs.test.RunTest.main(RunTest.java:31) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.intellij.rt.execution.application.AppMain.main(Unknown Source) Maybe we relly need a new Log4J implementation depending on its version this is bad, isnt it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
I guess you have not seen this: http://logging.apache.org/log4j/docs/api/org/apache/log4j/package-summary.html nor this http://marc.theaimsgroup.com/?l=jakarta-commons-devm=108436289322053w=2 At 10:09 PM 5/17/2004, robert burrell donkin wrote: i am more than a little confused about this whole issue. i've taken a look in cvs and priority still seems to be in existence (and undeprecated). when i looked at the gump record for sunday, common-logging seems to have passed. can someone please either explain where the log4j changes are and when the failure occurred? (as for the suggested patch) i'd be very unhappy about committing a patch which broke backwards compatibility with the most common versions of log4j (especially this close to a release). in fact, i'd probably think about vetoing any such change. there are a number of important upcoming releases who would be directly effected by these changes as well as a very large number of users of these releases who would be forced to upgrade. probably the right solution would be to create three different log implementations each targeted at a major log4j version and use some sort of reflection to work out which to use. this isn't very difficult to do but i'm not sure how gump would handle this, though. any ideas about gump-friendly build strategies for this? - robert On 17 May 2004, at 17:05, Ceki Gülcü wrote: Still no news on this item? On 2004-05-13 17:20:38 Adam R. B. Jack wrote: From: Mario Ivankovits [EMAIL PROTECTED] wrote: Just for the records - i already posted a patch, maybe a logging-committer might pick it up http://issues.apache.org/bugzilla/show_bug.cgi?id=28933 Excellent, thank you. I really hope one of the commons logging folks will get to it today, and we can have a fuller Gump tonight. There is some good activity on projects infrequently Gumped, and I'd like to see that momentum continue. regards, Adam -- Ceki Gülcü For log4j documentation consider The complete log4j manual ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ceki Gülcü For log4j documentation consider The complete log4j manual ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
At 10:33 PM 5/17/2004, Mario Ivankovits wrote: The change was in the Category class, formerly the log methods accepted a priority but this has change to a level now. But it looks like the change isnt really backward compatible, i have tried this now and got the following exception (patched commons-logging and log4j-1.2.8): java.lang.NoSuchMethodError: org.apache.log4j.Logger.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V at org.apache.commons.logging.impl.Log4JLogger.fatal(Log4JLogger.java:161) at org.apache.commons.vfs.test.RunTest.main(RunTest.java:31) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.intellij.rt.execution.application.AppMain.main(Unknown Source) The above looks wrong to me. Are you sure you don't have stale classes around during compilation? Maybe we relly need a new Log4J implementation depending on its version this is bad, isnt it? Don't gump the gun yet. -- Ceki Gülcü For log4j documentation consider The complete log4j manual ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
On 17 May 2004, at 21:47, Ceki Gülcü wrote: I guess you have not seen this: http://logging.apache.org/log4j/docs/api/org/apache/log4j/package- summary.html technically it's a recommendation rather than a deprecation which is why i was asking :) nor this http://marc.theaimsgroup.com/?l=jakarta-commons- devm=108436289322053w=2 i suspect that's filed with the 256 messages that i've still to read on the log4j list. (all the cross posts seem to get filed in my log4j directory.) please take into account that most old hands on jakarta commons use filtering extensively to ensure they have some time to do coding (rather than just reading mailing lists). cross posts may well be filed into low priority directories. unless the rules of the commons-dev mailing list are observed and prefixes are added to subjects, posts have a large chance of being ignored. i'd like to change the title of this thread very soon so that the other folks interested in commons-logging improved their chances of response. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
please take into account that most old hands on jakarta commons use filtering extensively to ensure they have some time to do coding (rather than just reading mailing lists). cross posts may well be filed into low priority directories. unless the rules of the commons-dev mailing list are observed and prefixes are added to subjects, posts have a large chance of being ignored. i'd like to change the title of this thread very soon so that the other folks interested in commons-logging improved their chances of response. Yup, I need to look into whether Gump can respect this list's prefixing. I agree, us humans ought. ;-) regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
On 17 May 2004, at 22:14, Adam R. B. Jack wrote: please take into account that most old hands on jakarta commons use filtering extensively to ensure they have some time to do coding (rather than just reading mailing lists). cross posts may well be filed into low priority directories. unless the rules of the commons-dev mailing list are observed and prefixes are added to subjects, posts have a large chance of being ignored. i'd like to change the title of this thread very soon so that the other folks interested in commons-logging improved their chances of response. Yup, I need to look into whether Gump can respect this list's prefixing. I agree, us humans ought. ;-) i've added some more filters so that the gump messages for the commons should move into a directory i'm likely to look at (rather than in with all the other failures which i'm less likely to look at). - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
On 17 May 2004, at 21:33, Mario Ivankovits wrote: robert burrell donkin wrote: i am more than a little confused about this whole issue. i've taken a look in cvs and priority still seems to be in existence (and undeprecated). when i looked at the gump record for sunday, common-logging seems to have passed. can someone please either explain where the log4j changes are and when the failure occurred? (as for the suggested patch) i'd be very unhappy about committing a patch which broke backwards compatibility with the most common versions of log4j (especially this close to a release). in fact, i'd probably think about vetoing any such change. there are a number of important upcoming releases who would be directly effected by these changes as well as a very large number of users of these releases who would be forced to upgrade. Ceki Gülcü wrote: Fortunately, the required changes are easy and are backward compatible. Commons-logging code needs to be changed as follows. The change was in the Category class, formerly the log methods accepted a priority but this has change to a level now. But it looks like the change isnt really backward compatible, i have tried this now and got the following exception (patched commons-logging and log4j-1.2.8): (as i read the language specification 2.0 anyway) this change should be compile compatible but not binary compatible. (i think that the cause is that in java the method overload algorithm is executed at compile time - see sections 13.2 and 15.2.) nice if ceki (or someone else from log4j) could confirm that this change is incompatible. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
Adam R. B. Jack wrote: It seems that Priority has been deprecated for a while, and this is a permanent API change. Is commons-logging willing/able to follow suit and make the change? If I understand correctly, using Level ought work with a wide range of log4j code. Even if you aren't ready to make a release, could you update CVS HEAD? Just for the records - i already posted a patch, maybe a logging-committer might pick it up http://issues.apache.org/bugzilla/show_bug.cgi?id=28933 -- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
From: Mario Ivankovits [EMAIL PROTECTED] wrote: Just for the records - i already posted a patch, maybe a logging-committer might pick it up http://issues.apache.org/bugzilla/show_bug.cgi?id=28933 Excellent, thank you. I really hope one of the commons logging folks will get to it today, and we can have a fuller Gump tonight. There is some good activity on projects infrequently Gumped, and I'd like to see that momentum continue. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [GUMP@brutus]: jakarta-commons/commons-logging failed
By the way, commons-logging developers could issue a maintenance release of c-l now, months before log4j 1.3 is released. At 09:55 AM 5/12/2004, Ceki Gülcü wrote: Hello, All hail gump. The use of Priority has been deprecated for over 2 years and it will be removed in log4j 1.3. Fortunately, the required changes are easy and are backward compatible. Commons-logging code needs to be changed as follows. Lines such as getLogger().log(FQCN, Priority.FATAL, message, t ); need to be changed to getLogger().log(FQCN, Logger.FATAL, message, t ); There 5 or 6 such lines in commons-logging. Note that the resulting commons-logging code will run on both log4j 1.2.x and 1.3 I hope this helps, At 12:56 AM 5/12/2004, Paul Smith wrote: Hi All, Not sure if this will get sufficient attention without bringing it here, so doing so... Yes, there has been a few changes under the hood in log4j recently. We'll have to chat internally to see what we can do, and get back to you. All hail gump for picking it up. cheers, Paul Smith -- Ceki Gülcü For log4j documentation consider The complete log4j manual ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ceki Gülcü For log4j documentation consider The complete log4j manual ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: jakarta-commons/commons-logging failed
To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project commons-logging has an issue affecting its community integration. This issue affects 143 projects, and has been outstanding for 6 runs. The following are affected: - avalon-activation-api : Avalon's main repository. - avalon-activation-impl : Avalon's main repository. - avalon-composition-api : Avalon's main repository. - avalon-composition-impl : Avalon's main repository. - avalon-composition-spi : Avalon's main repository. - avalon-logging-impl : Avalon's main repository. - avalon-logging-log4j : Avalon's main repository. - avalon-logging-logkit-api : Avalon's main repository. - avalon-logging-logkit-datagram : Avalon's main repository. - avalon-logging-logkit-impl : Avalon's main repository. - avalon-logging-logkit-socket : Avalon's main repository. - avalon-logging-logkit-syslog : Avalon's main repository. - avalon-logging-spi : Avalon's main repository. - avalon-phoenix : The Avalon Application Server Kernel - avalon-repository-cli : Avalon's main repository. - avalon-repository-main : Avalon's main repository. - barcode4j : Barcode4J --- for generating barcodes. - beepcore : BEEP is a new Internet standards-track protocol - castor : Java to XML, SQL, LDAP bindings - commons-attributes : Commons Attributes - commons-beanutils : Bean Utilities - commons-betwixt : Commons Betwixt Package - commons-cli : Commons CLI Package - commons-configuration : Jakarta commons - commons-digester : XML to Java Object Configuration - commons-discovery : Commons Discovery Package - commons-el : Expression Language - commons-fileupload : Commons File Upload Package - commons-httpclient : HTTP Client Library - commons-httpclient-2.0-branch : HTTP Client Library - commons-id : Commons Identifier Package - commons-jelly : Commons Jelly Package - commons-jelly-tags-ant : This is a Jelly interface for Ant. - commons-jelly-tags-antlr : This is a Jelly interface for Antlr. - commons-jelly-tags-avalon : This is a Jelly interface for avalon. - commons-jelly-tags-bean : A tag library for mapping tags to beans using a similar appr... - commons-jelly-tags-beanshell : This is a Jelly interface for BeanShell. - commons-jelly-tags-betwixt : This is a Jelly interface for Betwixt. - commons-jelly-tags-bsf : This is a Jelly interface for the Bean Scripting Framework. - commons-jelly-tags-define : This is a Jelly taglib for defining new tags and tag librari... - commons-jelly-tags-dynabean : This is a Jelly taglib for defining new tags and tag librari... - commons-jelly-tags-email : This is a Jelly interface for Email - commons-jelly-tags-fmt : This is a set of Jelly i18n tags. - commons-jelly-tags-html : These Jelly tags can scrub commons errors in HTML syntax. - commons-jelly-tags-http : These Jelly tags provide a simple XML syntax for HttpClient. - commons-jelly-tags-interaction : This is a Jelly interface to the user. - commons-jelly-tags-jetty : These are Jelly tags that can set up an in-process web serve... - commons-jelly-tags-jms : This is a Jelly interface for the Java Message Service. - commons-jelly-tags-jsl : The Jelly Stylesheet Library (JSL) - commons-jelly-tags-junit : The Jelly Unit Test Tags - commons-jelly-tags-log : The Jelly Logging Tags - commons-jelly-tags-quartz : This is a Jelly interface for the Quartz Scheduler. - commons-jelly-tags-soap : This is a Jelly interface for SOAP. - commons-jelly-tags-sql : This is a Jelly interface for SQL - commons-jelly-tags-swing : This is a Jelly interface for configuring Swing applications... - commons-jelly-tags-swt : This is a Jelly interface for configuring Swing applications... - commons-jelly-tags-threads : A library for processing Jelly scripts using multiple thread... - commons-jelly-tags-util : This is a set of Jelly utility tags. - commons-jelly-tags-validate : This is a Jelly interface for XML validation. - commons-jelly-tags-xml : ??? - commons-jelly-tags-xmlunit : This is a Jelly interface for unit testing XML applications. - commons-jexl : Commons Jexl Package - commons-latka : Functional Testing Suite - commons-messenger : A web based JMS framework - commons-modeler : Modeler MBeans - commons-resources : Commons resources - commons-services : Basic Services Architecture - commons-validator : Validation Framework - commons-vfs : Commons VFS - commons-xo : Jakarta commons sandbox - depot-update : Depot -- repository tools and more... - depot-update-ant-sample-httpclient : Depot --
RE: [GUMP@brutus]: jakarta-commons/commons-logging failed
Hi All, Not sure if this will get sufficient attention without bringing it here, so doing so... Yes, there has been a few changes under the hood in log4j recently. We'll have to chat internally to see what we can do, and get back to you. All hail gump for picking it up. cheers, Paul Smith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
This seems to be the result of a change in the log4j class org.apache.log4j.Category. An API-change has been made, but I'm not sure if this is a permanent change. Perhaps ceki can shed some light on this. See cvs: http://cvs.apache.org/viewcvs.cgi/logging-log4j/src/java/org/apache/log4j/Category.java Ted Husted wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project commons-logging has an issue affecting its community integration. This issue affects 239 projects, and has been outstanding for 4 runs. The following are affected: - ant-embed-optional : Java based build tool - avalon-activation-api : Avalon's main repository. - avalon-activation-impl : Avalon's main repository. - avalon-composition-api : Avalon's main repository. - avalon-composition-impl : Avalon's main repository. - avalon-composition-spi : Avalon's main repository. - avalon-logging-impl : Avalon's main repository. - avalon-logging-log4j : Avalon's main repository. - avalon-logging-logkit-api : Avalon's main repository. - avalon-logging-logkit-datagram : Avalon's main repository. - avalon-logging-logkit-impl : Avalon's main repository. - avalon-logging-logkit-socket : Avalon's main repository. - avalon-logging-logkit-syslog : Avalon's main repository. - avalon-logging-spi : Avalon's main repository. - avalon-phoenix : The Avalon Application Server Kernel - avalon-repository-cli : Avalon's main repository. - avalon-repository-main : Avalon's main repository. - barcode4j : Barcode4J --- for generating barcodes. - beepcore : BEEP is a new Internet standards-track protocol - bootstrap-ojb : ObjectRelationalBridge - castor : Java to XML, SQL, LDAP bindings - checkstyle : Java style checker - checkstyle-test : Java style checker - cocoon : Java XML Framework - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-linotype : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-mail : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-php : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-portal : Java XML Framework - cocoon-block-portal-fw : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-scratchpad : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slide : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-swf : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-webdav : Java XML Framework - cocoon-block-woody : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - cocoon-lenya : Content Management System - commons-attributes : Commons Attributes - commons-beanutils : Bean Utilities - commons-betwixt : Commons Betwixt Package - commons-cli : Commons CLI Package - commons-configuration : Jakarta commons - commons-digester : XML to Java Object Configuration - commons-discovery : Commons Discovery Package - commons-el :
[GUMP@brutus]: jakarta-commons/commons-logging failed
To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project commons-logging has an issue affecting its community integration. This issue affects 239 projects, and has been outstanding for 5 runs. The following are affected: - ant-embed-optional : Java based build tool - avalon-activation-api : Avalon's main repository. - avalon-activation-impl : Avalon's main repository. - avalon-composition-api : Avalon's main repository. - avalon-composition-impl : Avalon's main repository. - avalon-composition-spi : Avalon's main repository. - avalon-logging-impl : Avalon's main repository. - avalon-logging-log4j : Avalon's main repository. - avalon-logging-logkit-api : Avalon's main repository. - avalon-logging-logkit-datagram : Avalon's main repository. - avalon-logging-logkit-impl : Avalon's main repository. - avalon-logging-logkit-socket : Avalon's main repository. - avalon-logging-logkit-syslog : Avalon's main repository. - avalon-logging-spi : Avalon's main repository. - avalon-phoenix : The Avalon Application Server Kernel - avalon-repository-cli : Avalon's main repository. - avalon-repository-main : Avalon's main repository. - barcode4j : Barcode4J --- for generating barcodes. - beepcore : BEEP is a new Internet standards-track protocol - bootstrap-ojb : ObjectRelationalBridge - castor : Java to XML, SQL, LDAP bindings - checkstyle : Java style checker - checkstyle-test : Java style checker - cocoon : Java XML Framework - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-linotype : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-mail : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-php : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-portal : Java XML Framework - cocoon-block-portal-fw : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-scratchpad : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slide : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-swf : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-webdav : Java XML Framework - cocoon-block-woody : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - cocoon-lenya : Content Management System - commons-attributes : Commons Attributes - commons-beanutils : Bean Utilities - commons-betwixt : Commons Betwixt Package - commons-cli : Commons CLI Package - commons-configuration : Jakarta commons - commons-digester : XML to Java Object Configuration - commons-discovery : Commons Discovery Package - commons-el : Expression Language - commons-fileupload : Commons File Upload Package - commons-httpclient : HTTP Client Library - commons-httpclient-2.0-branch : HTTP Client Library - commons-id : Commons Identifier Package - commons-jelly : Commons Jelly Package - commons-jelly-tags-ant : This is a Jelly
