[GRADLE-1552] Eclipse plugin generates absolute filenames in .classpath for local jar files Created: 16/May/11  Updated: 04/Jan/13  Resolved: 22/Jun/11

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Bug
Reporter: Alan Krueger Assignee: Unassigned
Resolution: Not A Bug Votes: 0


I'm trying to port a NetBeans project over to Gradle and Eclipse. I've changed some of the common third-party libraries to be pulled down using Maven repositories but still have a couple of Jar files hosted locally within the sub-projects.

When creating Eclipse project descriptors, these local jarfiles are referred to using an absolute path on my system; this won't be suitable for committing to source control, as those directories won't necessarily work on other developer systems.

Comment by Alan Krueger [ 01/Jun/11 ]

We've moved toward not committing Eclipse project descriptors and requiring developers to run 'gradle eclipse' locally to prepare for using their IDE. This was necessary anyway to ensure their Gradle cache was preloaded with dependencies anyway.

Comment by Adam Murdoch [ 22/Jun/11 ]

We don't recommend checking the generated eclipse files into source control, and instead you should generate them where they are needed.

Alternatively, you can configure some path variables in the build script, which Gradle will substitute in the place of absolute path names. You would then have to define these path variables in each eclipse workspace.

Either way, I think we can close this issue.

Comment by Alan Krueger [ 22/Jun/11 ]

I agree. Curiously, there appears to be no way for the submitter to close this.

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