Order of copy resources/compilation different between M2E and Maven

[RoiSoleil]

When i try to build my project, i don't have the same result between M2E and Maven becasue Maven copies the resources before compiling the classes but M2E compiles the classes before copying the resources. How can I change that ? Is it a bug ?

[RoiSoleil]

@laeubi could you help ?

[laeubi]

Nope, JDT compiles the classes (with JavaBuilder), the m2e invokes all other mojos (with MavenBuilder)... it might be that you can control the order by the order of builders in the project file.

[mickaelistria]

That said, maybe we should consider m2e splitting into 2 builders (pre-compile and post-compile). But that would be some non-trivial change to develop.

[RoiSoleil]

My current use case is an annotation processor reading a file from ressources copied into target. In maven, as the copy is done before the compilation its ok. But within Eclipse it can't read the file because the file has not yet been copied.

[laeubi]

Annotation Processors can be automatically be configured by m2e in JDT if that is not working then maybe thats the problem here.

That said, maybe we should consider m2e splitting into 2 builders (pre-compile and post-compile). But that would be some non-trivial change to develop.

My goal on the long run is more to disable the JDT builder and let maven do all the work.

[mickaelistria]

My goal on the long run is more to disable the JDT builder and let maven do all the work.

You mean basically making the Maven builder capable of supporting incremental builds?

[RoiSoleil]

I created this sample project : https://github.com/RoiSoleil/annotation-process-not-working-in-m2e to illustrate the difference between maven and m2e. Should i create an issue.

[laeubi]

I created this sample project : https://github.com/RoiSoleil/annotation-process-not-working-in-m2e to illustrate the difference between maven and m2e. Should i create an issue.

From your example you are using a "workspace annotation processor" that is something not supported by JDT/m2e (yet) implementing this is probably not trivial. Contributions are of course always welcome :-)

[RoiSoleil]

Yes it's not the "workspace annotation processor" difference i wanted to show. Even if you close the "annotation-processor" module (maven build before). The resulting ClassA.txt is not found because the resssources are copied after the build.

[laeubi]

As a workaround I think it would work to put the resource in the main/java folder (even though this is not "maven style") then JDT should copy it before compile.