[GRADLE-1257] Expose a publicTestCompile configuration to depend upon Gradle tests when developing an external module Created: 19/Dec/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9-rc-3
Fix Version/s: None

Type: Improvement
Reporter: Tomer Cohen Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: Text File publicTestCompile.patch    

Comment by Frederic Simon [ 19/Dec/10 ]

Clarify the environment:
When developing an external Gradle plugin, it easier to reuse the test platform used inside Gradle build itslef.
The core.gradle build file exposes today a testCompile ivy configuration which is used by most internal Gradle plugins tests.
The attached patch is creating a new Ivy configuration "publicTestCompile" which contains all the spock dependencies used by Gradle tests, and the actual test helper classes present in core test source.
Once this Ivy configuration is exposed, with one line in our gradle file:

testCompile(group: 'org.gradle', name: 'gradle-core', version: '0.9+', configuration: 'publicTestCompile')

We are ready to write spock tests for our plugin.

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