Serge, Noel, Shipa, Steve, If I'm hearing this correctly, you're having trouble with some comps from Avalon-Cornerstone (Cornerstone) and/or Avalon-Excalibur (Excalibur). I'd like to try to help here if I can. If you guys can work on the deficiencies in the impls of these components, then I'd be happy to apply the diffs back to the the appropriate place of the source tree. If is obvious that the things you're fixing are equally useful to the other major socket using applications that sit on Avalon-Phoenix (FtpServer, Enterprise Object Broker, soon to be OpenORB, AvalonDB, Hypersonic Block, Cornerstone's excellent transport package).
There are basically two choices at the moment - one of you fixes the bug in Avalon prefixed CVS, without the rights to shove it back; OR we grant commit rights for one of the old-timers and you shove back your own changes. Building Excalibur and Cornerstone. Excalibur has had a huge amount of work spent on it in the past. We've broken out the packages but still allowed a central build. See http://cvs.apache.org/viewcvs/jakarta-avalon-excalibur/. There are many places where you'll have to rename ant.properties.sample to ant.properties, but that is fairly well reported on by the build process as you run across them. You could try jumping straght to the sub-dir that contains the package your want to modify, it may compile immediately, but there is possibility of dependancy, which again should be indicated by the build process. Besides the dependancies are illusatrated in dependancies.txt (root). Cornerstone (http://cvs.apache.org/viewcvs/jakarta-avalon-cornerstone) is easier to build, but represents the older way where there are multiple blocks in one source tree. Should be compilable though. If you have problems on the setup, I'll be more than happy to help. Assuming you get thru that, I'd be more than happy to apply diffs. If Avalon commit rights are needed, I can help with introductions for a JAMES committer to our happy family :-)) Lastly, a third strategy could be to wait for one of the Avalon newbie's to fix it. There are loads more people using one or more Avalon sub projects in propretory solutions (Content servers, poor man's EJB), and they are supplying quite a few diffs at the moment, it is only a quation of time until someone finds the same issue ;-) Regards, - Paul H -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
