Custom Domain Jitpack Deployment about simple-yaml HOT 5 CLOSED

This seems related to #70. I think I solved it removing the build from Jitpack and then triggering it again.

I guess it is something with Jitpack, because when I triggered the build it was correct and the pom in https://jitpack.io/me/carleslc/Simple-YAML/Simple-Yaml/1.8.4/Simple-Yaml-1.8.4.pom existed, but now suddenly it doesn't, so it started causing problems to retrieve the dependency. Maybe is something with Jitpack cache? Build passed and is green (https://jitpack.io/#me.carleslc/Simple-YAML), but the pom related to that version does not exist anymore, and because the build is green in Jitpack, it does not trigger a new build by its own.

However, com.github.Carleslc groupId still works, so it can be used as an alternative to retrieve the dependency.

from simple-yaml.

This seems related to #70. I think I solved it removing the build from Jitpack and then triggering it again.

I guess it is something with Jitpack, because when I triggered the build it was correct and the pom in https://jitpack.io/me/carleslc/Simple-YAML/Simple-Yaml/1.8.4/Simple-Yaml-1.8.4.pom existed, but now suddenly it doesn't, so it started causing problems to retrieve the dependency. Maybe is something with Jitpack cache? Build passed and is green (https://jitpack.io/#me.carleslc/Simple-YAML), but the pom related to that version does not exist anymore, and because the build is green in Jitpack, it does not trigger a new build by its own.

However, com.github.Carleslc groupId still works, so it can be used as an alternative to retrieve the dependency.

You can just use com.github.Carleslc instead of a custom domain since it doesn't really matter to have a custom domain for it and more stable.

from simple-yaml.

One of my dependencies which I do not control uses the me.carleslc custom domain resulting in gradle not being able to resolve it when building my project.

from simple-yaml.

One of my dependencies which I do not control uses the me.carleslc custom domain resulting in gradle not being able to resolve it when building my project.

Now https://jitpack.io/me/carleslc/Simple-YAML/Simple-Yaml/1.8.4/Simple-Yaml-1.8.4.pom is working again (I've triggered a new build). But still don't know why jitpack removes files unexpectedly.

from simple-yaml.

Since it seems to be more stable, com.github.Carleslc.Simple-YAML is now specified in the README.
But me.carleslc.Simple-YAML groupId is still valid and supported.

from simple-yaml.