I am having some problems when using Gradle Eclipse with the
gradle-1.0-milestone-1 (I believe this also occurs in other versions) and am
wondering if there is a better way that the project should be configured or
if it is a bug. The problem occurs when a project needs to depend on
sourceSets.test.classes. In order to do this I have a configuration that
looks something like this:
dependencies {
compile project(':jar1')
testCompile project(':jar1').sourceSets.test.classes
}
When the eclipse task is ran it produces a .classpath file with an entry
that looks like this
<classpathentry kind="lib"
path="/home/rwinch/workspaces/gradle-play/project/jar1/build/classes/test"
exported="true"/>
The problem is that the classpath entry references the path that gradle will
output the classes to and not the path that eclipse outputs the files (bin).
This means that the project will not get built in Eclipse until a build with
gradle has been ran. Additionally it means that the code gets out of sync
since Eclipse is outputing the build to the bin folder.
I have been able to work around this issue by adding an eclipseClasspath
whenConfigured entry to remove the entry (it is still properly seen since
the project is included in the compile dependencies). I am wondering if
there is a better way to configure this and/or if I should log a JIRA.
Thanks in advance,
Rob Winch
