Berin Loritsch wrote:
>
>> Editorial comment: there are people who are actively trying to
>> build Avalon related components - if for no other reason than to
>> verify the correct operation of projects they care about (e.g. Ant)
>> or to identify things that other subprojects (e.g., james) may need
>> to be aware of at some point. At times, this requires a little bit
>> 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?

If so, the fact that these things happen doesn't concern me. What does concerns me, however, is when knowledge of such events and fail to spark a dialog. Particuarly, when this is all within the scope of a single project.

>> Who knows, this might even foster a bit more cooperation and
>> communication within the Avalon project.
>
> :)

Perhaps that smiley is a bit premature.

http://cvs.apache.org/builds/gump/2002-12-09/jakarta-avalon-phoenix.html

- Sam Ruby




--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to