Looks like this problem occurs under Maven 3 as well. I also tried:
<compilerArguments> <AauditXml>${basedir}/test-audit.xml</AauditXml> <AoutpurDir>${basedir}/target</AoutpurDir > </compilerArguments> but that just gives me: [ERROR] Compilation failure Failure executing javac, but could not parse the error: javac: invalid flag: /home/amrk/IdeaProjects/securemx/smx3.git/integration/launchpad-tests/test-audit.xml Usage: javac <options> <source files> use -help for a list of possible options -> [Help 1] [ERROR] -- Pull me down under... On Wed, Nov 18, 2009 at 10:35 AM, Mark Derricutt <m...@talios.com> wrote: > 'lo all, > > I'm starting to experiment with using some annotation processors in my > build and have the following compiler plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-compiler-plugin</artifactId> > <version>2.0.2</version> > <configuration> > <source>1.5</source> > <target>1.5</target> > <compilerArgument>-AauditXml=${basedir}/test-audit.xml > -AoutputDir=${basedir}/target</compilerArgument> > </configuration> > </plugin> > > However, when the build runs (using Maven 2.2.1), javac seems to get an > auditXml property set to "${basedir}/test-audit.xml > -AoutputDir=${basedir}/target" rather than two properties set to their > respective values, when I was using Maven 3 at home I don't recall seeing > this issue (about to try it here under M3 as well). > > Has anyone seen this behaviour before? > > > > > -- > Pull me down under... > >