[GRADLE-1628] Clean task doesn't delete classes directory if classesDir was set Created: 21/Jun/11  Updated: 25/Jan/17  Resolved: 25/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Bug
Reporter: Benjamin Muschko Assignee: Unassigned
Resolution: Won't Fix Votes: 1


This problem was discussed on the mailing list. In case you change the default classes directory the clean task doesn't delete the directory. Apparently, it only works on build/classes.

sourceSets.main.classesDir = file('../build/out/classes')

As a workaround it has to be cleaned "manually":

clean {
   delete sourceSets*.classesDir

Gradle should do this work automatically.

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 [ 25/Jan/17 ]

The `clean` task only deletes the build directory so there shouldn't be any issue. Setting the classes directory to a directory outside of buildDir is custom and will need to be added to the clean task.

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