> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]
>
> More interest, a couple of additional potential developers, and work
> starting
> on .NET container.  Goal is widest compatibility (i.e. will work with Mono
> and M$ .NET).
> 

Okay, so it now looks like:

The recently flurry of activity on the Avalon mailing lists has centered on
defining the next generation of Avalon containers and preparing a subsequent
roadmap.  With the dust beginning to settle, the Merlin project is poised to
be released and become the flagship Avalon container, supporting the Avalon
4 Framework and previous containers (Fortress and Phoenix).

Avalon Meta

In an effort to standardize the various meta-info schemes used in Avalon
containers, the avalon-meta project was created in the sandbox repository.
Originally developed under the Merlin container, the meta project will
combine the AMTAGS (Avalon Meta Tags) proposal and the original Merlin meta
model.  Consideration has also been given to directly adopting the attrib4j
project (http://attrib4j.sourceforge.net/).

Avalon + .NET

Work on a C# implementation of the Avalon framework accelerated this last
month.  There has been more interest, a couple of additional potential
developers, and work starting on .NET container.  The goal is widest
compatibility (i.e. will work with Mono and M$ .NET).


---

Any other clarifications?  If not, I'll add it to the wiki soon.

jaaron

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

Reply via email to