Maven Generated Sources Ignore Additional Compilation Issues

I would like to be able to auto-configure our eclipse projects to ignore the optional compilation issues using m2e, but I seem to be running into a m2e vs maven conflict.

If I use the build-helper-maven-plugin to add the source directories, that's great - I don't need to automatically add generated-sources/annotations

to my eclipse project. But if I do this, every time m2e updates the eclipse project (alt + f5), it removes any manual configuration I added to the original directories (including Ignore compilation issues).

So, currently my workaround is to manually add the generated source directories to eclipse projects so that I don't constantly return all these warnings on the generated code.

(In my case, using dagger, which has a lot of generated code, but in a wide variety of formats from the rest of our codebase, not based on java8, etc., so we get a lot of format and style warnings.)

One answer might be to try out annotation processing in m2e, but I've had problems with this in the past, conflicting with maven on the command line and other issues, and I'm not sure if it will solve this problem anyway. the selection in the list for the annotation processing mode lists the disadvantages.

Can anyone think of any other workarounds until the bug is fixed ?

+3


source to share


1 answer


Fixed a bug in M2E 1.6.2 (1.6.2 / Mars RC2).



+1


source







All Articles