The idea behind the eclipse plugin is that you can develop on a project.
Right now, I checked out a new version of a project I'm working on. Somebody messed it up
and now it doesn't compile. I want to edit the faulty classes in Eclipse but I don;t have any .project
files. So I run mvn eclipse:eclipse. That fails because the project doesn't compile.
Now I cannot fix the bugs because the plugin that should make metadata ABOUT the project
tries to compile it first which makes no sense.
I understand that test-resources should also be present in eclipse, but this solution limits
the usage of eclipse on maven projects and is not backwards compatible in my opinion.
I'd like to see this change reverted, and maybe add a comandline switch to include/exclude
test resources when generating project resources. Currently I think only a new mojo can do the trick
since the @execute phase is not runtime configurable.
Maybe it's time to review the generate-test-resource phase. Is it per definition necessary to have
compiled src/main sources present in this phase? If so, why? If not, shouldn't the generate-test-(re)sources
be run right after the process-resources? I.e. move them before the compile phase?
Another solution might be to make the @execute phase configurable somehow, and specify an option
to the eclipse:eclipse plugin to NOT generate test resources and stick with the generate-resources