| [m2e-users] Project specific compiler warnings |
|
Hi, I have a few different projects some which are normal Java/Maven projects and some which are Eclipse plugins using Maven/Tycho. We have different compiler warnings setup for each project using the “compilerArgument” configuration but M2E
doesn’t seem to look at this setting and just uses the global compiler warning settings from Eclipse. Is it possible to get M2E to look at this flag and automatically put the correct settings in .settings/org.eclipse.jdt.core.prefs? Or if this is not possible – is it possible to tell M2E to copy certain settings to this file when importing
the project? We currently do not check in any of the .project, .classpath or .settings files to SCM – or is that the only way to achieve it? It would be nice to be able to manage this in the pom.xml so projects could inherit the compiler settings from the parent pom, and also the compiler warnings in the developers IDE would match what happens on the build box. David |