[GRADLE-2000] eclipseClasspath does not generate correct .classpath for Scala Created: 13/Dec/11  Updated: 04/Jan/13  Resolved: 26/Nov/12

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-6
Fix Version/s: 1.3-rc-2

Type: Bug
Reporter: Jeppe Nejsum Madsen Assignee: Unassigned
Resolution: Fixed Votes: 0


Due to changes in the Scala-IDE for Eclipse plugin (2.0), the classpath generated with eclipseClasspath is not correct when using the Scala plugin:

1) The Scala libraries should be added as a container entry
<classpathentry kind="con" path="org.scala-ide.sdt.launching.SCALA_CONTAINER"/>

2) The dependencies from the scalaTools configuration should not be added to the .classpath as a) this is included in the container above and b) the Scala-IDE plugin will refuse to build with e.g. two scala-library on the classpath

This will cause a problem if the Scala version used in scalaTools is different than in the Scala-IDE, but this is bound to give problems anyway

Comment by Iain Hull [ 24/Jul/12 ]

I was affected by this issue too Jeppe Nejsum Madsen has posted a workaround here:


Based on the workaround it shouldn't be too hard to fix in the core plugins. I would really like this fixed, as my team are planning to move to gradle from and and are current java and eclipse users.

Comment by Ben Manes [ 21/Nov/12 ]

Fixed in v1.3; should be closed.

Generated at Wed Jun 30 12:10:03 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.