You're right it was supposed to be <AoutputDir>, however thats just
the annotation processor option, one thing I noticed in the compiler
plugin docs is that it equates:
<compilerArgument>-verbose -bootclasspath
${java.home}\lib\rt.jar</compilerArgument>
with
<compilerArguments>
<verbose />
<bootclasspath>${java.home}\lib\rt.jar</bootclasspath>
</compilerArguments>
</configuration>
which implies that the contents of the <bootclasspath> subelement are
appended SPACE delimitered after the key, and not with an equals sign
as I expected, and that would explain the javac problem. Using
<compilerArgument> alone with only ONE -Axxx=fff setting works fine,
its when I add two.
I'm pulling down the compiler plugin source to see if I can spot whats
it, or I am doing wrong.
--
Pull me down under...
On Wed, Nov 18, 2009 at 12:08 PM, Wayne Fay <wayne...@gmail.com> wrote:
>
> > <AoutpurDir>${basedir}/target</AoutpurDir >
> >
> > [ERROR] Compilation failure
> > Failure executing javac, but could not parse the error:
> > javac: invalid flag:
>
> Isn't that supposed to be <AoutputDir> ? Is that the invalid flag that
> javac is complaining about?
>
> Try "mvn -X ..." to see the full line being passed to javac, then copy
> and paste that line into your own CLI and make sure it works. If not,
> tweak in CLI until it works, then tweak Maven config.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
