[GRADLE-585] Clean task does not clean the internal repository Created: 08/Aug/09  Updated: 04/Jan/13  Resolved: 24/Nov/10

Status: Resolved
Project: Gradle
Affects Version/s: 0.7
Fix Version/s: 0.9-rc-1

Type: Bug
Reporter: Steve Appling Assignee: Adam Murdoch
Resolution: Fixed Votes: 0


The clean task cleans the build directory, but does not remove files from the internal repository at .gradle/internal-repository. This can cause strange errors in multi-project builds where one person gets very different results than another based on their history in the project even after a clean.

This was causing strange problems for me with the Java multiproject sample. See Jira GRADLE-584 for more info.

Comment by Adam Murdoch [ 08/Aug/09 ]

Another solution to this problem would be to get rid of the internal repository, and resolve the inter-project artifacts directly from the build dir.

Comment by Hans Dockter [ 19/Aug/09 ]

You probably know this already. To clean the internal repository you can do the -C rebuild. Removing it by clean might be a better way of doing things, but I'm not sure. Let's say you only want to build a particular subproject. You want to do this with a clean. Do you want a rebuild of all the projects its depends on? I agree with Adam that getting rid to the internal repository all together would be nice. But this would give us basically the same behavior as we have now. For partial builds a clean would only clean the subproject. For a full build we upload the newest versions to the internal repository anyway.

Comment by Steve Appling [ 19/Aug/09 ]

I like Adam's solution better too. My goal was that if I ran a clean on a particular subproject, it's artifact(s) would be removed from the internal repository.

We had an issue where different developers with identical source were getting different test resuls after a clean build. Removing the internal repository fixed the issue (which I still don't understand), but I didn't feel that this should have been necessary.

Comment by Adam Murdoch [ 02/Oct/09 ]

Internal repository no longer exists, so this should fix this problem

Generated at Wed Jun 30 11:33:41 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.