The patch we're working with on issue9 highlights the need for this.
We could create one module that tests the processor with guice on the
dependency class path, and one without (assuming we ever figure out how to
filter out the build-environment copy - but I digress).
We could also use one module to test the maven-processor-plugin, one using the
compiler plugin, and one using the apt-plugin.
Original issue reported on code.google.com by james.ta...@jrtechnical.com on 14 Dec 2011 at 2:29
Original issue reported on code.google.com by
james.ta...@jrtechnical.com
on 14 Dec 2011 at 2:29