[GRADLE-1150] Executing junit test with missing testRuntime lib throws "Test process 'Gradle Worker 1' FAILED" Created: 14/Sep/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 0.9 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | René Gröschke (Inactive) | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Attachments: | pwmock.zip |
Description |
I've attached a project with a build file and a JUnit test. Executing "gradle test" on this project fails with the following error message:
The junit test uses powermock and needs "javax.el:el-api:1.0" to run successfully. If this lib isn't in the testRuntime classpath, gradle fails with the error message above. Classpath issues on tests should never cause gradle to fail. |
Comments |
Comment by René Gröschke (Inactive) [ 14/Sep/10 ] |
the -S output looks like the following:
|
Comment by René Gröschke (Inactive) [ 14/Sep/10 ] |
the output of a running this build from intellij gives more informations:
|
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 [ 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. |