Re: [cf-push] Deploying spring-music twice will throw lots of warnings

Daniel Mikusa <dmikusa@...>

Running `gradle clean` isn't sufficient. That only cleans out your project folder. It speed up builds Gradle/Maven will download JAR dependencies and cache them outside of your project folder. These essentially sit there forever. If there is a problem downloading a JAR dependency and it's corrupted, the corrupted JAR will sit there forever. You need to manually clean it out.

>For Maven, you just have to wipe out the offending files under ~/.m2/repository (or delete everything under that folder). I'm not as familiar with Gradle, but SO says it stores them under ~/.gradle/caches/modules-2/files-2.1, The solution should be the same. Delete the offending files or just delete everything. Then run `gradle clean` and `gradle assemble` again. You should see it download the files again. Make sure you're on the network & able to access the files it's trying to download.


On Tue, Apr 21, 2020 at 2:32 AM "何贵民(箫竹) <guimin.hgm@...> wrote:

Hello Daniel, 

Thanks for your feedback. I have run the `gradle clean` and `gradle assemble`, but unfortunately, after that, the issue still exist. Is there any more ideas? It is important for our customers and us, I am looking forward to your help eagerly. Thanks for in advance.

Thanks and warm regards
Guimin, He

Join to automatically receive all group messages.