> The changes were not in Phoenix but in cornerstone and were done at the > request of a James developer IIRC (Was it Greg?). Obviously there was a > disconnect when updating James.
Whom?? (http://jakarta.apache.org/james/weare.html) For what it is worth, we were pretty amenable to whatever changes Avalon was making, since Paul Hammant had volunteered to help change our code to keep in synch with Avalon. Then there were some more changes to Avalon, and Paul froze which versions of Avalon "stuff" we were using. I don't recall at the moment all of the compatibility issues. I think that Component was, at least at one point, one of them. Now, Paul probably has his fingers poised to reply, "Dude, there is no Avalon. There is Avalon-Frameworks, Avalon-Phoenix, Avalon-Cornerstone, and ...", and that is the problem. From another way of looking, there is only Avalon, and multiple packages that it ships. Avalon should bee responsible as a community for all of the changes it makes, and the changes it imposes upon client code. In any event we are pretty current on Phoenix. We are backlevel for the moment on Cornerstone. Since we are trying to put out a Release Build, we have been reluctant to make the change until that is cut. We'll do the update. For one thing, I'd like that fix I posted for the thread pool limits. --- Noel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
