Hello guy, this is intended behavior. Resource files are part of your classpath and the compileTestJava task is executed again if its classpath changed. For example, imagine you have simple spring bean definitions stored as xml resources you want to reuse in your tests. I’m sure you want to run your tests again after you have changed the bean definitions.
We surely want to rerun the tests when the production resources change, but why recompile the Java test files? Compilation of Java test sources is not affected by changed production resources.
Hi etienne, you’re right. There was a misunderstanding on my site. Executing tests again is intended, but recompiling the tests seems redundant here. Technically spoken, the reason for recompiling the test classes is, that the classpath of the tests has changed and gradle does not (yet) differ if classes or resources have changed. We might create an issue for this.