[GRADLE-939] src/test/resources not added to classpath intermittently Created: 14/May/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: Daniel Bower Assignee: Unassigned
Resolution: Won't Fix Votes: 3

Attachments: File exampleProj.tar.gz    

 Description   

There is one test in the attached project. It fails the majority of the time. At some point, after repeated reruns, the test will pass, every time after that it will pass, until the next gradle clean.

It is failing while testing the readConfiguration call in Application.groovy:
ClassLoader.getSystemResource("config.properties");
a file in src/test/resources

At one point I thought that it would run successfully if I commented out the test, run gradle test (letting it complete successfully), uncomment the test, run gradle test again, and then it would pass again, but this was not reproducible beyond 2 attempts.

 Comments   
Comment by Daniel Bower [ 21/May/10 ]

When I dropped the config file down into a package, the expected behavior occurred. The config.properties file showed up on the class path. So this is either a work around or intended behavior: In src/test/resources, files must be in a package, to show up on the test classpath.

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