[GRADLE-3053] Setting testLogging.showStandardStreams property always results in "true" Created: 26/Mar/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


I'm having a hard time understanding the behaviour of the following build script (using gradle 1.11) while trying to set the showStandardStreams property for unit test execution. My complete build script is as follows:

apply plugin: 'java'

test {
boolean b = false
println "Property value before set: " + testLogging.showStandardStreams
testLogging.showStandardStreams = b
println "Property value after set: " + testLogging.showStandardStreams

If you then execute a gradle task (for example, 'test'), the following output is produced:

Property value before set: false
Property value after set: true
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test UP-TO-DATE


I've tried setting the property to have a Boolean type (rather than the intrinsic boolean), and even setting it to itself, but nothing makes a difference: as soon as the property is assigned, it becomes true.

Thanks for any insight,


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:38:37 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.