[GRADLE-2368] Eclipse plugin loses java source folder. Created: 29/Jun/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
In a setup where java sources and other resources are kept in the same folder and separated by include directives, the eclipseClasspath task fails to generate a classpathentry node for the actual java sources.
Consider the following build.gradle file:
The affected gradle version will generate the following .classpath file:
It should generate this instead:
|Comment by Christian Graefe [ 29/Jun/12 ]|
Sorry. As it turns out, Eclipse does not allow multiple classpathentry nodes with the same path attribute. Still, just falling back to the last seen filter setting might not be the way to go.
|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.