[GRADLE-1079] Eclipse .classpath generation should not force users to manually create a GRADLE_CACHE classpath variable Created: 29/Jul/10 Updated: 04/Jan/13 Resolved: 01/Jan/12 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9.1 |
| Fix Version/s: | 0.9-rc-3 |
| Type: | Improvement | ||
| Reporter: | Chris Beams | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 1 |
| Description |
|
Repro steps:
This is seemingly minor but represents a significant usability departure from what folks are used to with plugins like m2eclipse. It's one thing to say 'all you have to do is type gradle eclipse' and import your projects. It's another to force the user to go into preferences, etc. A reasonable workaround would be simply generating fully-qualified paths to the users home directory. This is ugly too, but assuming that people don't check in their .classpath files, it shouldn't be a problem. Doing it this way should at least be an option. |
| Comments |
| Comment by Hans Dockter [ 29/Jul/10 ] |
|
As stated in the (not yet uploaded user's guide). Soon we will have autogeneration of the classpath variables. What you can do in any case is to remove the GRADLE_CACHE variable from the EclipseClasspath task. Then absolute paths will be used: eclipseClasspath.variables = [:] |
| Comment by Adam Murdoch [ 28/Dec/10 ] |
|
This was fixed in 0.9-rc-3 |
| Comment by Chris Beams [ 28/Dec/10 ] |
|
Thanks, Adam. |
| Comment by Szczepan Faber [ 01/Jan/12 ] |
|
reopened to remove the invalid duplicate info |
| Comment by Szczepan Faber [ 01/Jan/12 ] |
|
This issue was fixed by using absolute paths instead of GRADLE_CACHE |