[GRADLE-2192] CompileTestJava is executed when resource in main source set is modified. Created: 22/Mar/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1



we observed that if we change a resource file inside the main source set the compileTestJava is executed. Shouldn't this task be up to date?

:edoras-bpm-execution-core:compileJava UP-TO-DATE
:edoras-bpm-execution-core:zipDependencies UP-TO-DATE
:edoras-bpm-execution-core:compileApiJava UP-TO-DATE
:edoras-bpm-execution-core:processApiResources UP-TO-DATE
:edoras-bpm-execution-core:apiClasses UP-TO-DATE
:edoras-bpm-execution-core:checkstyleApi UP-TO-DATE
:edoras-bpm-execution-core:processTestResources UP-TO-DATE
:edoras-bpm-execution-core:checkstyleTest UP-TO-DATE


Comment by Gradle Forums [ 22/Mar/12 ]

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.


Comment by Gradle Forums [ 22/Mar/12 ]

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.

Comment by Gradle Forums [ 22/Mar/12 ]

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.

Comment by Benjamin Muschko [ 15/Nov/16 ]

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!

Comment by Benjamin Muschko [ 10/Feb/17 ]

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.

Generated at Wed Jun 30 12:15:13 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.