AspectJ and the Plexus core

Howdy,

I meant to post this soon after the AspectJ 1.1 release but got bogged
down.

At any rate now that AspectJ 1.1 has been released I would like AspectJ
to play a bigger role in Plexus.

Right now most of the components that are present as part of Plexus are
Avalon compliant. That is totally cool and I have no problem with that
as it's a good starting point. But I have some requirements that I need
satisfied for Tambora but they are specific to Tambora.

What I would like to be able to do is easy mutate a whole set of
components to work the way I need them to. I want to do something with
security and it crosscuts all the components I'm using.

I want to create a base component class that is empty so I have a known
location for introduction. So if I wanted to mutate the hierarchy for
all my components I can do so in a single location. 

AspectJ 1.1 now supports storing aspects in JARs and applying aspects to
a set of binary JARs. So I can create whatever aspects I like for my
particular need and apply them across all my components.

So basically what I would like to do is add the AspectJ runtime to the
standard Plexus deployment.

I will augment the Plexus plugin to support the mutating of components
and it will use the maven AspectJ plugin which I'm going to update for
the RC1 release of Maven.

If there are no objections, I will start the work this weekend. I would
like AspectJ to be an integral part of Plexus and with the 1.1 release
of AspectJ I believe there are no downsides.

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