avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farr, Aaron" <Aaron.F...@am.sony.com>
Subject RE: Avalon Versions
Date Mon, 12 Jul 2004 20:03:11 GMT

> -----Original Message-----
> From: Niclas Hedhman [mailto:niclas@hedhman.org]
> Where is the technical problem between AF v4.1.5 and v4.2?
> 1. No change in the AF code itself.
> 2. A Specification Clarification that 4.2 components can declare the
> Life cycle artifacts in their constructor, instead of the phased
> population. Containers that does not support this feature, will not be
> considered 4.2 compatible.
> 3. All 4.1.x components will work in 4.1.x and 4.2 compliant containers.
> 4. Avalon is saying to its users; "Framework is NOT enough to declare
> a compatible component contract. Containers SHOULD go beyond
> Framework, and Avalon is providing the tools." You are free to use or
> ignore this recommendation.

I think this is where the confusion starts.

During the vote for 4.2, most of us believed it was some relatively minor
changes to the framework.  The notes during the vote were as follows:

      * incorporating the changes introduced to the configuration
        impl from Leo Sutic concerning the addition of a modifiable
        configuration api and implementation
      * updated license

That's it.

If someone can find some more elaborate release notes or a change log I
would love to see it.

Now it is being asserted that 4.2 implies not only these code changes, but a
more dramatic change to the definition of the Avalon platform.  This has
been expressed in a number of ways including the now infamous constructor
injection docs.

Several of us feel that if this change from "Avalon Framework is all there
is" to "Framework is NOT enough" is not necessarily a bad thing (I think
it's a Good Thing) but that is constitutes more than just a 4.1 to 4.2 jump.

So you see, I think Berin, Leo, and I all feel a bit "blind-sided."  Perhaps
we were sleeping at the wheel.  It doesn't matter now.  The important thing
is that work it out.

J. Aaron Farr
  (724) 696-7653

To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message