As mentioned in http://wiki.gradle.org/display/GRADLE/Gradle+1.0-milestone-4+Breaking+Changes, it's now necessary to use "tasks.eclipse.dependsOn(cleanEclipse)". Thanks for catching the outdated docs, we'll update them shortly.
PS: For some reason, your post never got through to the mailing list. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw jameswiltshire wrote: > > Just upgraded to 1.0M4 and found some unexpected behaviour around the > Eclipse plugin. I see from the release notes that a lot of refactoring has > been done around the IDE plugins. > > In 1.0M3 and earlier you could add task dependencies to the eclipse task > by using 'eclipse.' > eclipse.dependsOn(cleanEclipse) > > In 1.0M4 this code throws an error, as 'eclipse' is no longer a Task, but > is an EclipseModel object instead. > "Cause: No signature of method: > org.gradle.plugins.ide.eclipse.model.EclipseModel.dependsOn() is > applicable for argument types: (org.gradle.api.DefaultTask_Decorated) > values: [task ':cleanEclipse']" > > Simple workaround for the above issue is to obtain the Task object from > the project > tasks['eclipse'].dependsOn(cleanEclipse) > > Wondering if this is now the expected behaviour? The 1.0M4 docs still > mention "eclipse.dependsOn(cleanEclipse)" as an example of how to disable > merging (section 29.4.1.1). > > Thanks > James Wiltshire > -- View this message in context: http://gradle.1045684.n5.nabble.com/eclipse-object-is-no-longer-a-task-in-1-0M4-tp4650437p4658855.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
