Niclas Hedhman wrote:
Gang,
I am trying to put all the "community issues" aside and distill what are the technical objections to;
-----------------------
<issue>
AF4.2 allows component authors to request a supply of the LifeCycle artifacts (Context, ServiceManager, Configuration) as constructor injections instead of classic styled phased injection.
</issue>
Just a minor point .. s/instead/in preference to
I don't think that even LSD can concoct a case where this introduces a component incompatibility. If there is a valid case of a 4.1 component written which won't work with this, then we deal with it.
It also implies that AF4.2 compliant containers need a little bit tweaking.
(Please observe that Merlin's feature of injecting just about anything into the constructor parameters, are not part of the framework specification.)
-------------------------------
<issue>
Concerned has been raised that Avalon Framework has lost visibility on the new web site.
</issue>
Personally, I am willing to either place a "AF4.1" link under Central, pointing to the old docs, or including Framework in the Products column on the home page pointing to the relevant current section of the component specification, i.e. LifeCycle specification and/or the javadocs. PROVIDED, that all this hoo-haa settles down and instigation stops from all sides (I'm glad I'm not on PMC anymore).
I'm ok with putting a AF4.1 link under Central. I'm not ok with Framework under Products. I am also ok with updating existing docs with information that clearly associates versions with sementic descriptions.
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]
