[GRADLE-2481] idea and eclipse classpaths may not work out implicit task dependencies Created: 17/Sep/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
If some dependencies are provided via a buildable file collection, like that:
Then eclipse and idea will not work out that 'foo' task needs to be executed. The reason is ide plugins resolve configuration at execution time and then it's too late to run any task as the graph has already been built. In other circumstances this problem can be resolved by using @InputFiles annotation.
Specify explicit task dependency: ideaModule.dependsOn ... eclipseClasspath.dependsOn ...
|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.