Stephen, what should that tell me: You spread the refactoring not only to the core and sub-system but also onto meta, repo, util, etc?
Avalon Meta was initially within the Merlin system (back in 2.1). It was moved out to a separate Avalon level package and in that process things like tags, APIs, implementation, docs, tools, etc. all evolved and improved. That system (meta 2.0) was then factored back in to Merlin as part of the 3.0 release.
Avalon Repository was initially based on the repository model within Merlin 3.0. It was separated out to better handle generic systems embedding with a priority on minimal footprint and ease of configuration. The refactoring the repository sub-system by Alex resulted in the separation of a set of common utilities (covering property aggregation, criteria handling, exception reporting, and access to environment variables). Merlin 3.2 was refactored as a system established by the repository facility, leveraging the vastly improved embedded support.
Merlin 3.3 (a.k.a. CVS HEAD) incorporates model listeners, the internal kernel pluggable facilities management, and the improved thread model. Commit level on 3.3 is rather low. Merlin 3.4 (a.k.a V-3-4 branch) is addressing a number of aspects related to the meta-model, in particular a review of specific classnames to address easier recognition of function, the shifting of assembly logic from the runtime to the model, and security aspects.
Du you think you can convince me to change oppinion with this comment?
Just making sure you have the right information available.
Cheers, Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
