Date
1 - 4 of 4
[cf-push] Deploying spring-music twice will throw lots of warnings
"何贵民(箫竹)
Dear Cloud Foundry Community,
I am Alibaba Cloud developer and I am working on integrating Alibaba Cloud with CloudFoundry. Now, I happened an issue when I deploy app spring-music: https://github.com/cloudfoundry-samples/spring-music, and I need your help. The issue as following: when I run command cf push to deploy spring-music firstly, it can be deployed successfully;
when I run command cf push again, it throw many warnings, as following: Staging app and tracing logs... My cf cli version is 6.51.0+2acd15650.2020-04-07. In addition, about this issue, I have asked help in several days ago by slack cf-deployment channel: https://cloudfoundry.slack.com/archives/C2U7KA7M4/p1586335015016800 and capi channel: https://cloudfoundry.slack.com/archives/C07C04W4Q/p1586480456093000 , but there are no any reply. Looking forward to your help. Thanks and warm regards
Guimin, He
|
|
Daniel Mikusa <dmikusa@...>
This has happened to me in the past when Maven/Gradle fails to download a JAR dependency and it gets stuck in the local cache on my laptop's filesystem. The actual file is some error, not a JAR file, which is why you get messages about invalid JAR files. 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, https://stackoverflow.com/a/33196481. 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. Hope that helps! On Mon, Apr 13, 2020 at 11:08 PM "何贵民(箫竹) <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 |
|
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, https://stackoverflow.com/a/33196481. 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. Dan On Tue, Apr 21, 2020 at 2:32 AM "何贵民(箫竹) <guimin.hgm@...> wrote:
|
|