[GRADLE-2975] IDEA plugin produces invalid .iml file WRT source sets for IDEA 13 Created: 09/Dec/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: | 6 |
Description |
If I use the "ideaModule" task against a new Intellij 13 .iml file, it breaks some of the new settings for "resources" and "test resources". Below is a snippet of my .iml file. NEW (this is the new Intellij 13 format for "Mark as" sources). You can now mark directories as: Sources, Tests, Resources, Test Resources, Excluded. The old format was only: Sources, Tests, and Excluded. <?xml version="1.0" encoding="UTF-8"?> GRADLE OLD. The Gradle idea plugin reverts the IML file back to the old format. This causes an error in Intellij 13 because I now have the same "resources" included in two different locations (you can see an example of that below). You can see in the format above the "type" attribute is dropped and the format is restructured. The plugin is basically breaking the new formatting in the configuration. <?xml version="1.0" encoding="UTF-8"?> The idea plugin also removes any assigned "module dependencies". This is gradle version 1.8, intellij version 13, java 1.7.45. |
Comments |
Comment by Shawn Kovalchick [ 15/Aug/14 ] |
I can confirm that this still occurs with Gradle version 1.11 and IntelliJ version 13.1.4 |
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. |