J Aaron Farr wrote:
Release 4.2.0 of the Avalon framework as presented in the vote and release did not mention constructor injection. see:
http://marc.theaimsgroup.com/?l=avalon-dev&m=108324047317944&w=2 http://marc.theaimsgroup.com/?l=avalon-users&m=108415482904649&w=2
Just for clarification - constructor based injection was proposed as part of our roadmap, specifically identify avalon-framework 4.2 as the target for inclusion of constructor injection. There were no objections or drama raised with respect to that point (in fact at appeared to be warmly received). What is perhaps more interesting is that the action represented zero change existing api documentation and zero impact on the api - itself reflecting the issues of fragmented documentation which have now been addressed. Please note also that we explicitly bumped the version from 4.1.X to 4.2 because of the semantic supplement.
As for my bullet pointing of this item - yep I'm at fault - its not in the email your referenced simply because the email was put together by going though the cvs and aggregating the details of changes between the prior releases and all of the candidates (involving checking all changes and potential impact of version numbers).
Constructor injection *was* mentioned in respect to Merlin 3.3.0 which happened to be released at the same time:
Kind of natural - it's the container that is responsible for doing the work of object instantiation in synchronization with an underlying framework 4.2.
Cheers, Steve.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
