I agree, it makes sense to move Chainsaw to its own module.
OK. I'll create a module called 'logging-chainsaw' or do you prefer another name?
I'm not as enthusiastic about making Chainsaw a subproject - I'm not against the idea, but I think the developer community (hey, 2 or 3 is a community, right?) is too small to pass LS or Apache's expectations for a self-sustaining project.
As long as there is a long term commitment by the developers, there is nothing wrong with a project having 2 or 3 developers. I don't foresee Scott or Paul abandoning the development of Chainsaw in the near future. As Chainsaw is already part of Apache, spawning it as a separate sub-project of Logging Services is a simple formality. Moreover, as a separate project, it could grow more or less independently of log4j.
Either way, I will support a decision reached by Paul and Scott on this matter. (They do the work, they get to decide.)
Hopefully that will change..
I've been thinking about starting work on an Eclipse plugin version of Chainsaw.
Sounds good.
-- Ceki G�lc�
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
