[GRADLE-1394] When selecting JUnit/TestNG within test task, it would be useful to have option to add embedded version to test classpath Created: 22/Feb/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9-rc-1, 0.9-rc-2, 0.9-rc-3, 0.9, 0.9.1, 0.9.2
Fix Version/s: None

Type: Improvement
Reporter: Spencer Allain Assignee: Unassigned
Resolution: Won't Fix Votes: 0


For better or worse, in the past gradle revealed the junit jar file onto the classpath for compileTestJava. The classloader isolation now makes sure that doesn't happen.

Now in order to compile Junit tests, some instance of junit jar file needs to be found in a separate repository. It would be very nice to have some way of saying useJUnit(['embeddedGradleLibs' : 'true']) or something to that effect saying that you'd like to compile tests against the version of JUnit that ships with gradle and will be used at runtime.

Obviously there are cases where you want to have some fixed version of JUnit/TestNG, but it used to be so convenient to have small standalone projects that didn't need to define any repositories to be able to run the test cases.

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