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.

regards,
René

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.

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.