Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-1079

Eclipse .classpath generation should not force users to manually create a GRADLE_CACHE classpath variable

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: 0.9.1
    • Fix Version/s: 0.9-rc-3

      Description

      Repro steps:

      1. check out project
      2. gradle eclipse
      3. eclipse->import existing projects into workspace
      4. notice errors about build classpath
      5. fix problem by going eclipse->preferences->classpath variables and adding a GRADLE_CACHE variable

      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.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            cbeams Chris Beams
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: