[GRADLE-2592] Generated eclipse .classpath includes non-jar entries that lead to errors on import Created: 10/Dec/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 2


See also the linked forum ticket.

Some dependencies resolve to non-jar files (e.g. xmls, jsons). Eclipse plugin puts them in .classpath as lib entries and this leads to errors on import.


Until the bug is fixed, you can:

1. Configure the whenMerged rule and filter out unwanted entries:

plugins.withType(JavaBase) {
  plugins.withType(EclipsePlugin) {
    eclipse.classpath.file.whenMerged { classpath ->
      classpath.entries.removeAll { it.path.endsWith('xml') }

2. Manually fix the entries after import.

Comment by Gradle Forums [ 10/Dec/12 ]

It might be a bug, I'll push this to jira.

For the time being, you can work around by excluding offending artifacts at the dependency level or using the IDE dsl ([1]http://gradle.org/docs/current/dsl/or...).

Hope that helps!
[1] http://gradle.org/docs/current/dsl/org.gradle.plugins.ide.eclipse.model.EclipseClasspath.html

Comment by Tim Bain [ 25/Sep/13 ]

If the dependency was a non-JAR file that was intended to be loaded as a resource at runtime (e.g. an XML config file that was to be read by the program), then removing the classpath entries would be incorrect behavior, and fixing this "bug" would actually introduce a bug.

If we do anything that prevents dependencies from being added to the classpath, it should be something that can be configured, perhaps with a set of dependency types (IvyDE does something similar, where you can specify a comma-separated list of file extensions) or some other mechanism. But the idea that only JARs can/should ever go on the classpath is a flawed one, and I'm not even completely sure that users might not want POMs to be available on the classpath under some circumstances. We can make intelligent default that work for most users, but ultimately any change to this behavior needs to be configurable to allow use cases outside of the majority case.

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 12:26:07 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.