On Sat, 2005-03-26 at 17:23 -0500, Noel J. Bergman wrote: > Remy wrote: > > > My plan for JULI is to: > > What is JULI? I know JCL, UGLI, Log4J, j.u.logging ... hmmm ... is JULI an > acronym for j.u.l-integration? > > > Is there any pace for this in the logging project, or should I > > seek another home ? > > If not in Logging, perhaps in Jakarta Commons? It appears that we have > several folks trying to move JCL to the next level, and both you and Richard > Sitze ahould have considerable common ground in terms of needs.
there seems to be considerable and ongoing controversy about scope when it comes to allowing the development of logging components here. when it comes to looking at richard's proposal's, i do admit that this is one of the reasons why i've been reluctant to take any action in this area. but i do think that these projects should be able to find a home somewhere at apache there has been talk of the possibility of logging.apache.org inviting JCL to move there. i have also offered karma to any folks from logging who want to influence development here. the logging.apache.org team certainly know a lot more about logging than myself (and i'd guess most of the rest of the team here) but probably aren't as familiar with the needs of bricks as the people here or as knowledgeable about containers (of all sorts) as remy. is JCL out of scope for jakarta commons since it deals with logging or in scope since it's focused on bricks? is eJCL out of scope for jakarta since it deals with logging or in scope because it focuses on the logging needs of reusable serverside J2EE components? would JULI be out-of-scope for jakarta since it deals with logging or in scope since it's focused on solving the particular logging issues associated with containers? i don't really feel qualified to give an answer. it would be great if someone could find a way through the politics and history... - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
