Where the source of the wiring information comes from and how it's
used in Plexus is completely decoupled.
What you see for Plexus components does not necessarily hold true for
Mojos because the intent is to allow the client, in this case the Mojo
system, to define its own APIs and wiring information. Plexus was
designed to provided a pluggable plugin mechanism :-) Mojos, our Maven
plugins system, is just one of them.
The best approach to annotations for Mojos is a patch that's sitting
in JIRA which is long overdue in applying but allows Mojos to use 1.5
annotations. It was written by the Artifactory author and they use it.
On 23-Mar-08, at 10:49 PM, Benson Margulies wrote:
I defined a new Mojo by extending AbstractCompilerMojo from the
maven-compiler-plugin.
It doesn't work, because the @component annotation for the compiler
manager
on AbstractCompilerMojo doesn't happen.
Obviously, it works in the CompilerMojo.
As an experiment, I made a copy of AbstractCompilerMojo co-located
with my
Mojo class. That works.
The only information I've managed to scavenge suggested that plexus
annotations don't work on base classes at all, so I'm stumped.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
