[GRADLE-630] suiteXmlBuilder does not allow access to project properties Created: 10/Sep/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Marcus Better Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: File gradle-testng-params.tar.gz    

 Description   

The TestNG builder does not handle references to project properties, for example as parameter values. Instead of the value, a string like "groovy.lang.ExpandoMetaClass$ExpandoMetaProperty@71d0e17a" is substituted.

I'm trying to pass a parameter like this:

        suiteXmlBuilder().suite(name: 'suite') {
            test(name: 'test') {
                parameter(name: 'foo', value: bar)
                packages {
                    'package'(name: 'org.example')
                }
            }
        }

where bar is a project property.

In the attached test case, "gradle test" fails with 

java.lang.AssertionError: expected BAR, got groovy.lang.ExpandoMetaClass$ExpandoMetaProperty@71d0e17a
        at org.example.ParamTest.test(ParamTest.java:12)

If the project property bar is replaced with the string constant "BAR", the test succeeds.

 Comments   
Comment by Hans Dockter [ 28/Sep/09 ]

As a work around you can do:

parameter(name: 'foo', value: this.bar)

This is an issue with closures and delegation. The this keyword has a special meaning when used within closures, in particular within nested closures (see: http://groovy.codehaus.org/Closures). We will think about how to improve this for 0.9.

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 11:34:51 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.