Re: Notice of scheduled work

Hi,

On Fri, 18 Jul 2003 07:49 am, Jason van Zyl wrote:
> > I guess things got delayed. After the Avalon stuff disappears, is the
> > idea that plexus users will create their own component interfaces and
> > build a lifecycle around them, or will plexus have its own set of
> > interfaces that define a different component lifecycle?
>
> The lifecycle is completely configurable. Dan is going to maintain the
> Avalon container API which uses Avalon nomenclature. What I'm adding is
> not going to be a whole lot different I'm just removing Avalon from the
> core.

We were planning on doing something similar for loom. Essentially create a 
lightweight stripped down framework similar to Avalon to use internally. 

Though we haven't really discussed it what I wanted to do was essentially take 
best bits out of Avalon and rewrite them. In practical terms this meant

* Remove Version
* Remove ExceptionUtil
* Remove Cascading*
* Remove Re* lifecycle stages
* Remove all deprecated crapola
* Merge Initializable/Disposable/Startable into interface "Active" or 
something
* Simplify implementations and put them in a separate package

Would you be interested in doing this together. To be honest I didn't want to 
make it part of the public API or document it but it is not that much extra 
work to get it as a free standing library.

Thoughts?

-- 
Cheers,

Peter Donald
 "Man's mind stretched to a new idea never goes back to its original 
dimensions." -Oliver Wendell Holmes