Noel J. Bergman wrote:

I agree that we shouldn't make current users feel disenfranchised, but we
can do that in such a way that doesn't promote the framework as an Avalon
product.


The Framework defines the core contracts between components and the
container (as well as utilities).  Layered on that are reusable components,
and then we have containers.  This comes across as little more than a tactic
to disenfranchise people who don't share the Merlin vision.

Noel:

This is not a "Merlin vision" question. It's a issue concerning the defintion of a component model - that is the central subject. The framework does not *define* the component model - it is only a *part* of the picture.



There must be another way than what has been flaming over the dev
and pmc lists the last few days.


Yes there is.  I will quote myself:

  So far, the view has been that the consequences of forking from
  Frameworks up are not desirable.  If that is still true, then
  there is no choice but for everyone to suck it up, behave like
  intelligent respectful adults and collaborate to find a consensus
  that satisfies everyone.  That may be code, that may be packaging,
  it may be a combination of things.  Just grow up and find it.

  Either that, or fork from Frameworks on up and take the consequences.
  Personally, I recommend and would prefer the former to seeing the
  fallout from the latter.


here's how we envision its use in the new Avalon


Who is "we"?  If you are intending to drop compatibility with other Avalon
products such as Excalibur, etc., I suggest that we move Frameworks from the
stewardship of Avalon to Excalibur.

Wow - that's interesting idea!

Excalibur defined its specialization of "component model" as did Phoenix. Avalon's progress on a component model is NOT defined by the Excalibur nor Phoenix semantics. It is carefully evolving a component model respecting backward compatibility and in the process filling in several undefined aspects.

In Excalibur wants to do something different - then they can just do it. Just remember - it will not be Avalon.

Stephen.

        --- Noel


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--

|---------------------------------------|
| Magic by Merlin                       |
| Production by Avalon                  |
|                                       |
| http://avalon.apache.org              |
|---------------------------------------|

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to