logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Glezen" <pgle...@us.ibm.com>
Subject RE: Version 1.2
Date Tue, 06 Nov 2001 16:48:49 GMT
Hi Scott,

I understand that "real world" product schedules don't run on the "It's
finished when it's finished" project management paradigm.  That sometimes
makes for a bit of a mismatch when a project (open source or not) depends
on a future development of another open source project.

There are a couple of things I don't understand about your situation.

Are you saying that you are having to change JBoss to run with log4j 1.2
whereas you don't have to now?  What in JBoss needs to change?

Also, if log4j 1.2 were declared ready today, would it be usable for you?
If so, why not check the sources out, run a build, and declare that your
version of log4j.

I haven't looked at the JMX support in log4j yet, though I will soon.  Are
your concerns isolated with the JMX support within log4j?

- Paul

Paul Glezen
Consulting IT Specialist
IBM Software Services for WebSphere
818 539 3321


Scott Coleman <scott.coleman@soltima.com> on 11/06/2001 08:11:45 AM

Please respond to "Log4J Developers List" <log4j-dev@jakarta.apache.org>

To:   "'Log4J Developers List'" <log4j-dev@jakarta.apache.org>
cc:
Subject:  RE: Version 1.2



Hi Paul

I have already been playing with JMX, and was half way through developing
JMX configuration for log4j, when I found that in 1.2 it was already
developed.
I wish to use version 1.2 with JBoss, which means changing JBoss to support
it. I do not think my manager will be to happy with this, therefore I was
requesting a release date so that I could determine when JBoss will support
it, or when they will let me check in new files. Maybe I should add a
factory method to allow both versions to run?

Regards
Scott

-----Original Message-----
From: Paul Glezen [mailto:pglezen@us.ibm.com]
Sent: Tuesday, November 06, 2001 4:23 PM
To: Log4J Developers List
Subject: Re: Version 1.2


Why can't you use the JMX configuration now?  Even if you're hesitant about
putting such a system in production, you could at least be playing with it
a bit, which you should do anyway before jumping in.

As for your question, the log4j releases haven't been scheduled in the
past.  They just happen when they are ready.  I don't want to sound
maliciously vague.  But it really is a matter of what has to be done and
who has the time to do it.

- Paul

Paul Glezen
Consulting IT Specialist
IBM Software Services for WebSphere
818 539 3321


Scott Coleman <scott.coleman@soltima.com> on 11/06/2001 06:03:13 AM

Please respond to "Log4J Developers List" <log4j-dev@jakarta.apache.org>

To:   "'Log4J Developers List'" <log4j-dev@jakarta.apache.org>
cc:
Subject:  Re: Version 1.2



Hi All

Does anyone know when version 1.2 will be fully ready. So that we can start
using the JMX configuration??

Regards
Scott

--
To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>




--
To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>




--
To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>


Mime
View raw message