Berin Loritsch wrote:
Niclas Hedhman wrote:
2. Timing. I am not comfortable of making a release of Avalon 5, Avalon Planet, without being able to deliver. We need ramp-up period, and it will take a fair amount of time.
Avalon 4.5? Big enough jump to get the message accross, yet not fully 5.0 to let you mature.
4.5 = 'allowance for component authors to use constructor injection of life cycle artifacts, that other AF4 containers are not interested in supporting'
Is that what you really mean?
If you oppose the constructor injection of life cycle artifacts, then spell it out, instead of all the mumbo-jumbo about how to solve a situation that has been created without looking at the issue.
It is not necessary, to jump to other conclusions that requires a fork. If you are really opposing the 'enhancement' for the component author, bring forward the reasons why this is such a bad thing.
1. I think it is great as component author to throw in the artifacts into the constructor.
2. I think (but not sure) that it can't be very hard for a container to support it.
So, again; Where is the problem with 4.2 ??
Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
