> the sole reason we still have excalibur and cornerstone is that the > commons project will not accept avalon-enabled components. > > I'd be happy if they would, we'd just migrate everything over to > commons, make all of avalon committers to commons, then start work on > integrating (taking the best pieces of the various implementations and > "avalonabling" all of it). > > The way I see it, Avalon Framework should be in very widespread use > across the Jakarta and XML projects. The way we capture complex design > issues in a small, solid framework is not found in any of the other > projects. > > Commons doesn't see it that way and feels any component that uses the > avalon framework interfaces as having an ugly dependency on some > external project.
AFAIK it all only about some avalon interfaces. If this is such a central point (and it really seems to be) why doesn't someone start a small commons project that simply puts these interfaces into a commons package. Since it is inside *commons* then every jakarta projekt should be able to use them. Of course not everybody wants to use a server, ... Regards, Ole -- Ole Bulbuk Tel.: 0331/74759/60 Ernst Basler + Partner Fax: 0331/74759/90 Tuchmacherstr. 47 E-Mail: mailto:[EMAIL PROTECTED] 14482 Potsdam WWW: http://www.ebp.de -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
