It shows up at the end of the 'gradle tasks' output as this: Pattern: clean<TaskName>: Cleans the output files of a task.
ie its a general purpose rule you can use on any task. On 30/11/2011, at 2:07 PM, Kenneth Kousen wrote: > Running "gradle tasks" doesn't show a cleanEclipseClasspath task. That's why > I always used cleanEclipse instead. Is there going to be a new task for the > eclipse plugin? > > Ken > > On Tue, Nov 29, 2011 at 9:17 PM, Daz DeBoer <[email protected]> > wrote: > Turns out this previously worked due to a bug in Groovy < 1.8. Milestone 6 > upgraded to Groovy 1.8, causing this breakage. > http://issues.gradle.org/browse/GRADLE-1953 > > Should be fixed in a milestone soon. Until then, please use "gradle > cleanEclipseClasspath eclipse". > Daz > > > On 29 November 2011 10:21, Kenneth Kousen <[email protected]> wrote: > For what it's worth, I had that issue long before milestone 6. I always run: > > gradlew cleanEclipse eclipse > > whenever I change my project dependencies. That's always worked for me. > > Ken > > > On Fri, Nov 18, 2011 at 6:28 AM, Russel Winder <[email protected]> wrote: > I am finding that I have to do: > > gradlew cleanEclipse && gradlew eclipse > > since trying to do: > > gradlew eclipse > > with a preexisting Eclipse set up leads to an inconsistent project > state. > > Is this as it is expected to be? > > Thanks. > -- > Russel. > ============================================================================= > Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] > 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > > > > -- > Kenneth A. Kousen > President > Kousen IT, Inc. > > > > > -- > Darrell (Daz) DeBoer > Principal Engineer, Gradleware > http://www.gradleware.com > > > > > -- > Kenneth A. Kousen > President > Kousen IT, Inc. > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
