> Why do you want to fork and continue development on a framework that is
> dead and buried by the Apache Foundation and its own creators?
The ASF didn't bury the framework, we close the community. The Avalon
community had degenerated into an unfortunate state of perpetual strife and
unwillingness to collaborate, and therefore, after years of trying to fix
it, was closed. Most of the active developers had already left to form
other, related, groups that didn't have the social problems. One such, for
example, is Apache Excalibur. Most of Avalon's components moved to the
Excalibur project. Other parts are available in Loom or elsewhere.
*IF* we need to make changes to the existing Avalon code, we CAN. At the
moment, we don't. Over time, we will most likely move off of Avalon, but
there is no urgency or need to rush. The current platform is stable,
functional, and tested.
That stability, in fact, one of the sticking points within the Avalon
community. Many users wanted the Avalon platform to remain stable, with
just bug fixes and incremental, compatible, improvement. Others wanted
radical API changes that would break existing code, but enable their vision
of new functionality. Avalon was closed in large part due to the inability
of the community to resolve those two viewpoints. It wasn't closed due to
the code.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
