Quoting Yoav Shapira <[EMAIL PROTECTED]>: > Hola, > > > How can we have confidence when the existing JCL causes so many > > problems for log4j users, especially when even the mere existence of > > these problems have been denied for so long? It seems unrealistic, > > doesn't it? > > I have confidence in the people (mentioned earlier, including us, the other > Tomcat folks, etc.) and the Apache brand. The JCL code itself will be gone, > replaced with our new creation, called JCL 2.0 for branding and adoption > purposes. >
So, is the only concern the brand name "JCL"? It seems to be. If the code is going to be completely different and not backwards compatible with the existing "JCL" it isn't really "JCL", so why call it "JCL"? Why not call it "UGLI"? And if it has to do with logging, why should it be a Jakarta project when there exists an official Apache logging services project? It seems to me that UGLI has already solved the problems that the proposed JCL 2.0 is supposed to solve. And if UGLI hasn't completely addressed all logging API issues, then why doesn't the JCL 2.0 team accept that there has already been work done to solve the problems they caused and apply their effort toward making sure that UGLI meets their needs? I don't mean for this to be flamebait. I'm just really perplexed as to why JCL 2.0 is needed now that UGLI exists? Note that if JCL had already solved the issues before UGLI, then UGLI wouldn't have to exist and we wouldn't be having this discussion. We'd simply being using a proper JCL, or maybe, more appropriately, "ALAPI" (Apache Logging API) or some such name. The fact that there still exists a group in Apache developing a logging API that continues to work outside the official logging services project is awefully strange as well. I can understand this between completely separate open source entities, but not within the same (Apache) organization. Very strange. Jake > Yoav > > > --------------------------------------------------------------------- > 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]
