[GRADLE-2749] sonarRunner test dependency Created: 12/Apr/13 Updated: 24/Jan/17 Resolved: 24/Jan/17
I use sonarRunner in my gradle build script and it works very well unless a unit test fails. In that case gradle will not execute the sonarRunner taks (even with the --continue option), because it implicitly depends on test. I would say that this implicit dependency should not be there and that users of the plugin need to be aware that the tests have run before. Or am I missing something?
|Comment by Gradle Forums [ 12/Apr/13 ]|
Good point. Previously, people complained that `gradle sonarAnalyze` does not run `compile` and `test`, but the situation you describe is the bigger evil. We may have to remove the task dependency, or change it into one of the new task relationships introduced in Gradle 1.6+. Meanwhile, you can get rid of the unwanted dependency with `tasks.sonarRunner.dependsOn = `.
|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:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 24/Jan/17 ]|
The Sonar Runner was removed from the Gradle core code base. It now exists an external plugin. Please open an issue there if you believe this is still an issue.