Re: Notice of scheduled work

On Thu, 2003-07-17 at 17:39, Mark H. Wilkinson wrote:
> 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?

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.

> 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.

The default has been the Avalon lifecycle. But if you wanted to add a
stage in the lifecycle you could, say, for security if you wanted.

> > 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.

AspectJ has actually been around for 5 years, but that being the case if
you don't want to use aspects you don't have to. The whole point of
aspects is that they are orthogonal to your base code. So what that
means is that you won't have any aspects and you won't use the aspectj
compiler. Those who wish to take advantage of aspects can. I'm just
putting the hooks in to enable the clean use of aspectj.

> > 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.

Yah, I've been living with some work arounds too.

> -Mark.
> 
> _______________________________________________
> Plexus-dev mailing list
> [email protected]
> http://lists.codehaus.org/mailman/listinfo/plexus-dev
-- 
jvz.

Jason van Zyl
[email protected]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society