[GRADLE-1297] while setting "buildDir" to external folder, the "eclipse" plugin will generate the invalid output path in the ".classpath" file. Created: 09/Jan/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9.1, 1.0-rc-3
Fix Version/s: None

Type: Bug
Reporter: island chen Assignee: Unassigned
Resolution: Won't Fix Votes: 0


for example, I set the "buildDir" to "file:///G:/GradleBuild/${name}", where the driver G: is a ram disk.

Gradle works well with "buildDir" set to external folder, but the exclipse will generate the ".classpath" file like the following:

<classpathentry kind="output" path="../../../G:/GradleBuild/test01/classes/main"/>
<classpathentry output="../../../G:/GradleBuild/test01/classes/main" kind="src" path="src/java"/>
<classpathentry output="../../../G:/GradleBuild/test01/classes/main" kind="src" path="src/groovy"/>

These classpathentries would not work with eclipse, since eclipse is not allow setting the output folder to the external folder directly. But we can define the output folder as a "Linked Folder" which links to a external folder, check http://stackoverflow.com/questions/1470827/external-output-folder-in-eclipse please.

So my suggestion is when the "buildDir" refers to a external folder, the eclipse plugin should use "Linked Folder" to handle the output folder.

Comment by Szczepan Faber [ 14/May/12 ]

The bug still persists in 1.0rc3

Comment by Szczepan Faber [ 14/May/12 ]

The bug still persists in 1.0rc3

Comment by island chen [ 01/Sep/12 ]

any update?

Comment by island chen [ 01/Sep/12 ]

get a solution from "http://www.tinhtruong.me/2012/03/put-build-directory-of-gradle-into-ram.html" could solve this issue!

Comment by Eron Wright [ 04/Apr/14 ]

As a potential workaround, you can influence the classpath entries by setting the pathVariables. The value is replaced with the key. For example:

allprojects {
    apply plugin: 'eclipse' 
    eclipse {
        pathVariables 'GRADLE_USER_HOME': gradle.gradleUserHomeDir
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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 11:51:59 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.