[GRADLE-1036] clarify documentation on how to set the an IDEA path variable in the ideaModule task Created: 15/Jul/10 Updated: 04/Jan/13 Resolved: 11/Aug/10 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9 |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Dan Tanner | Assignee: | Hans Dockter |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
In the idea_plugin section of the user guide, the documentation isn't clear on how to configure the ideaModule task to handle IDEA path variables. In my case, I'm trying to replace the hard-coded dependency path values in the generated iml to use an IDEA variable. p.s. Any chance you could add a comment with the solution for this until the released documentation can be updated? |
| Comments |
| Comment by Hans Dockter [ 02/Aug/10 ] |
|
You just need to define a variable in IDEA and IDEA will automatically replace absolute paths with the variable. This leaves the Gradle IDEA plugin with one problem. It can't do a proper merge now as it does not consider the modified entries from IDEA to be equal with the ones generated by Gradle, thus creating duplicates. The reason why you need to declare the IDEA variables for the Gradle IDEA plugin is that it can recognize those entries as equals. But the plugin does not use them to generate relative entries, this is left for IDEA (which is sometimes done with some delay). Maybe it would be better if the plugin would generate those variable entries directly like the Eclipse plugin does. |