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>
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).
-------------------------------
<issue> Avalon (Framework) compliance/compatibility </issue>
This seems to be perceived very differently. I (and Stephen) maintains that "Avalon 4" compliance doesn't exist, and no need to discuss it. We should talk about "Avalon Framework 4.x" or "Avalon 4.x Lifecycle" compliance/compatibility.
If everyone can agree on either of these terms, things are suddenly a lot easier to handle.
I would like to propose that we setup a page (if it doesn't exist) where the containers we know of are listed, and add columna (to start with) for various features.
1. AF4 LifeCycle.
2. AF4 LifeCycle Artifact Constructor Injection.
We can add more columns and containers as we go along.
We can't we get along?
Cheers Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
