Re: Notice of scheduled work

On Mon, 2003-07-14 at 01:58, Jason van Zyl wrote:
> Tomorrow night I am going to remove all references to Avalon code in
> Plexus. I'm not following the project anymore, anyone who I respected as
> a developer has in essence bailed and I don't think there's much to
> learn there anymore. So Avalon is going bye bye.

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?

Oddly enough, I'd never thought of defining a component lifecycle for
things myself. I guess I just assumed that the internal plexus.conf was
the way things were intended to be.

> I'm also going to do some cleanup work that Pete has suggested vis-a-vis
> using the aspect he created to test the release of components.

At the risk of appearing to be lagging behind on fashionable technology,
I'd hope that the core of plexus can remain aspect-free. My perception
is that aspects are still seen as bleeding-edge technology, and as such
might be difficult to justify in production systems.

> I'll probably also have time to get around to hiearchical containers
> this week too as I need it so that another tool I'm working on will
> function.

Oooh; now this I'm interested in. I've got my own hacks that fake
hierarchical plexus instances, but I'm reaching the limit of what can be
done without more significant changes to the plexus core.

-Mark.