Stephen McConnell wrote:Without Avalon Meta your ability to establish portable components goes out the window.
Nevertheless it is not a standard--it is a utility for Merlin.
Hi Berin:
That's an interestingly adaptive point of view keeping in mind your post [1] that initiated the extraction of the meta info layer from Merlin to a separate and independent package:
> All three of the Avalon containers have different > mechanisms for doing [meta-info persistence], and it > would be really great to *standardize* on one. So > far, Merlin has the most expressive format, so we > might want to use that format to handle the > integration. In fact, we might want to adapt that > whole library (the Merlin Meta) library to meet the > needs of all the containers.
That was back in July, things moved forward, meta was separated from Merlin, it was updated, changed, pushed around, tightened up, repackaged under the Avalon, and put up for vote as the Avalon Meta product, and published as the Avalon Meta package by the PMC in late September.
What this means is that it *is* Avalon' meta-info solution, our standard model for the expression of component meta information. There are three things you can do about that:
a) evolve it b) fork it c) remove it
Each with its associated process.
Finally, I would like to stress that the Avalon Meta package is not a utility. It is - in conjunction with framework 4.1.5 - an important step forward in the evolution of the Avalon Component Model (I'm quoting from from our website).
Stephen.
[1] http://marc.theaimsgroup.com/?l=avalon-dev&m=105759427015506&w=2
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
