> From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Sam Ruby > > Berin Loritsch wrote: > > > >> of cooperation - to this day, I still have been unable to locate > >> the correct place to find and build the > >> org.apache.avalon.framework.info classes. Any hints would be > >> appreciated. > > > > :/ > > > > Unfortunately, that was someone's planned library for future > > inclusion. It is not voted upon, and not released yet. > It was being > > developed in Excalibur (info?) > > So, let me see if I get this straight. The development version of > Phoenix (a.k.a., "the stable container") depends on something in the > sandbox. Furthermore, that something has already changed in > a way that > is incompatible with Phoenix's usage. > > Does this pretty much sum up the current state of affairs?
It seems so. People who have not been working on Phoenix really don't know what is going on with that project. I have subscribed to it, but with all the volume of Avalon dev, Avalon users, et. al. it is hard to notice when something like this happens. There may have been an anouncement that the change was going to occur, but I cannot vouch for that ATM. The problem is that ContainerKit was originally intended to be the aggregation of container utilities. The model was too rigid, and when Steve tried to make some changes, he got vetoed. He created the Meta package to correct what he thought were the mistakes. I believe I tried to get them to work together, but neither were really willing. Later, instead of working with the already set up ContainerKit, Peter created the Info to address what he thought was a better architecture. As to the technical qualifications of each of these, I can't say one way or the other. My focus had been on providing a better ECM with proper separation of concerns (aka Fortress). In the end I think we will all agree that ContainerKit should go the way of the graveyard as I don't think it is currently supported in any way. The question becomes do we work with Meta, Info, or a new tool? I think the consensus is to work with a new tool for new development. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
