ven if the log4j log level for that package is
at WARN, the 3rd party library would be doing the expensive
operation? Or does the JUL bridge pass the log4j configuration back
to JUL? If not, is that a reasonable feature to add?
Thanks,
Josh
--
Joshua ChaitinPollak
Software Engineer
Ki
Thanks for the answers, I guess from my point of view (limited I
know), everything is great, so release it! :)
Thanks again,
Josh
On Oct 30, 2007, at 5:23 PM, Paul Smith wrote:
On 31/10/2007, at 4:10 AM, Joshua ChaitinPollak wrote:
Thank you Paul! Your updated snapshot worked like a
group
'org.apache.logging' and log4j and log4j-component are in group
'log4j'. Any chance of those getting synced up? I know thats just
visual categorization, but its a bit funky.
-Josh
On Oct 29, 2007, at 10:32 PM, Paul Smith wrote:
On 30/10/2007, at 10:34 AM, Joshua ChaitinPollak wr
On Fri, 2007-10-26 at 07:59 +1000, Paul Smith wrote:
On 26/10/2007, at 5:26 AM, Joshua ChaitinPollak wrote:
If you had the time, crafting a unit test based on the other unit
tests in the bridge project would be most useful to demonstrate a
problem if there was one.. ?
Perhaps an example of your
a bit surprised.
-Josh
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
modifying the code anyway?
I tried to compile the bridge from source via Maven, but there were a
bunch of dependancies not available on the plugin maven poms. I've
taken to excluding the jmx dependancies in the pom, but there was an
problem with apache-log4j-component.jar
-
