Leif Mortenson wrote:
> Peter, > I am working on getting the instrument package working (replaces altprofile) > and was wondering what your plans were for how to setup interdependant packages > like this. > > The instrument sub-project will rely on avalon-framework, and logkit jars > as well as altrmi and a few xml jars for some of its features. Some of its > classes also extend classes in the excalibur/container package. > > Other packages will also make use of the classes in the instrument sub-project > to instument their functionality. The package will be used in a way similar > to how the logger classes are used. There has even been talk of adding this > into the ECM itelf to enable the profiling of lookups and releases of > components. One other option would be to do the following. The majority of the Instrument package does not rely on anything but the logging code in avalon-framework. The system does include an InstrumentComponentManager which extends the ECM. Eventually, I would like to simply merge its features into the ECM and get rid of it. This would allow the Instrument (AltProfile) features to be used by applications like Cocoon without requiring any changes. So for now I can create an instrument sub project which can build independently. But also include an instrument/component package in the all/scratchpad source tree which extends the ECM. The all package would then be dependent on the instrument sub project. Does this follow your line of thinking for how these interdependencies would be handled? It would be nice to keep the instrument/component package with the instrument sub project however. Cheers, Leif -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
