[GRADLE-2620] Eclipse classpath.file.whenMerged hook breaks confusingly for non-java projects Created: 09/Jan/13 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Description |
Comments |
Comment by Gradle Forums [ 09/Jan/13 ] |
Can you please provide the full error message. There's a section about which object the `whenMerged()` method is actually being called on missing. If in doubt, please just provide the whole output. |
Comment by Gradle Forums [ 09/Jan/13 ] |
Hi Luke. Here is the entire output including stack trace. nathan@deadveal:~/Development/Code/juzidian$ gradle eclipse --stacktrace FAILURE: Build failed with an exception.
BUILD FAILED Total time: 4.847 secs |
Comment by Gradle Forums [ 09/Jan/13 ] |
The problem is because classpath file is not generated for all projects but only for projects that have the java plugin (strictly speaking: the JavaBase plugin). To fix the problem you can: subprojects { The exception is not great. We should definitely improve Gradle's bahavior in this scenario. I'll create a jira ticket for it. Hope that helps! |
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. |