This issue must be really annoying to users, I agree. The way would be to find the exact commit in GitHub between Versions 3.1 and 3.2 which caused this issue. This means compiling the maven-compiler-plugin in a loop and testing the project attached over and over again.
On Thu, Jan 21, 2016 at 3:44 PM, Thomas Broyer <t.bro...@gmail.com> wrote: > On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian <agud...@apache.org> wrote: > > > ** New Feature > > * [MCOMPILER-203] - Allow compiler-plugin to specify annotation > > processor dependencies > > > > Great! But… > > I don't get how you can add a feature about annotation processors and not > at the same time fix one of the most annoying issue when using annotation > processors that generate Java sources: > https://issues.apache.org/jira/browse/MCOMPILER-235 > > Is everyone always doing clean builds? or everyone sets > useIncrementalCompilation to false? > (or maybe everyone actually still uses 3.1; along with the > build-helper-maven-plugin if they need the generated sources added as > source roots in downstream plugins) > > /me frustrated > -- Cheers Tibor
