Jason,
It seems to me, and I'm likely to be confused, that what we have here is a
collision of maven and plexus.
The maven-compiler-plugin is a thin wrapper on the plexus compiler system.
The plexus compiler system uses the plexus component model to add new
compilers. So, adding a new compiler in
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 i
I will JIRA a request to make the AbstractCompilerMojo into a component.
On Mon, Mar 24, 2008 at 10:12 AM, Stuart McCulloch <
[EMAIL PROTECTED]> wrote:
> On 24/03/2008, Benson Margulies <[EMAIL PROTECTED]> wrote:
> >
> > Ah. So one might imagine someone refactoring things so that all the
> > inje
On 24/03/2008, Benson Margulies <[EMAIL PROTECTED]> wrote:
>
> Ah. So one might imagine someone refactoring things so that all the
> injected
> fields of AbstractCompilerMojo were protected, so that an extending class
> in
> another plugin could have parallel annotations.
>
while that might look o
Ah. So one might imagine someone refactoring things so that all the injected
fields of AbstractCompilerMojo were protected, so that an extending class in
another plugin could have parallel annotations.
On 24/03/2008, Benson Margulies <[EMAIL PROTECTED]> 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
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 AbstractCompilerM