Re: Avalon Project Hierarchy

[Peter Royal]

On Wednesday, November 20, 2002, at 09:55  AM, Berin Loritsch wrote:

* Avalon Framework remains as is.  We can look at Avalon 5 later after
  the dust has settled.

this *MUST NOT CHANGE*. i realize the impetus that was behind the move to Serviceable and the dropping of the Component interface. IMHO, in hindsight, this was a VERY BAD idea. Not conceptually, but practically, because now everyone must move over or face massive deprecation warnings, which is not good. The empty marker interface could easily be provided by dynamic proxies. But what is done is done. we need to leave the A-F interfaces *SET IN STONE* so we have a foundation to build upon.

* Avalon Excalibur gets repurposed to strictly a location for Components.
All support code gets moved to commons (unless the move is already
done with Jakarta commons like in the case of Collections or replaced
by a more robust library like Concurrent).

I'd like to see Excalibur either

a) move to Apache Commons

or

b) have a separate committer list, so individuals from A-F consumer projects could be involved in the component library. Basically opening it wide up for wider involvement.

* As containers become mature, they move out of Avalon scratchpad and
become a top level sub-project. I.e. Avalon Fortress and Avalon Merlin
at the same level as Avalon Phoenix when they are released.

+1

* All components in Avalon Cornerstone get merged into Excalibur.  This
  means we have to come up with some standard Context name/value pairs
  that always exist--as this is the only reason why most cornerstone
  components require Phoenix.

+1

* I am not sure what to do with Avalon Apps. We need to look at the
possibility of moving them out of Avalon's sphere of responsibility.
I would have a hard time justifying their existence in an Avalon charter.
But we may also want to follow the same rules as containers for the
applications.

Agreed. Some things can go to the scratchpad (phyre, for one... kinda shelved for the moment unfortunately, but it will rise again!)
-pete

--
peter royal -> [EMAIL PROTECTED]


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