I have a project and a shared folder that is common to all my projects that includes classes that are not necessarily used (and therefore) complete for all projects. When executing the compile phase, it is erroring because some of the files in the shared folder which is added with the builder-helper-maven-plugin have missing dependencies because these files are not used in this particular project.
However, it appears that executing the target compiler:compile does a different type of compile, for one thing not executing the generate-sources phase. So i guess executing a specific target with maven does not execute all previous target in the lifecycle? It appears that running "mvn generate-source compiler:compile" works. It does not error on missing imports in uncalled classes. Can you clarify why the compile phase attempts to validate all classes in the src directories, including ones not used in the application? The eclipse builder for example does not attempt to validate all classes, while the intellij builder does I believe. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-errors-on-compilation-of-files-with-missing-imports-files-that-are-not-called-by-the-applicatie-tp5458721p5458721.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
