JitPack link 404s
See original GitHub issueThe JitPack link in README.md
404s. The directory seems to be there, and I see logs, but the artifact does not appear to be available. There are a couple warnings in the build log I looked at, but at the end it does list the artifact, so it would seem that it was created.
Link:
https://jitpack.io/com/github/frohoff/ysoserial/master/ysoserial-master.jar
To test:
user@localhost:~$ curl https://jitpack.io/com/github/frohoff/ysoserial/master/ysoserial-master.jar
Build failed. See the log at jitpack.io
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
JitPack is a novel package repository for JVM and Android ...
JitPack.io. JitPack is a novel package repository for JVM and Android projects. It builds Git projects on demand and provides you with ready-to-use ......
Read more >Plugin Portal Dependency Resolution Failing Due to JCenter ...
I noticed this because Jitpack builds are failing, ... my suspicion is that it is expecting JCenter to return 404s for packages not...
Read more >Now that Bintray and JCenter are shutting down, what should ...
Update: JitPack has clarified that the 404s were caused due to an infra issue. ... CLICK THIS LINK to send a PM to...
Read more >ANNOUNCEMENT: Android SDK finally here! - #15 by BCN
OK, sorry about that - the Tinker app for Android is now public, no more 404s. ... maven { url “https://jitpack.io” }
Read more >web-public / react-native · GitLab - Yunio
Summary: If you have following scenario 1. Have <Image> component with valid URL 2. Due to user action set <Image> to incorrect URL...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Still works for me but I can see from https://www.uptrends.com/tools/uptime that it seems to be returning a 404.
Wonder if it could be a CDN cache problem. I’ll see what I can do.
No problem. I just remembered having a similar issue a few months ago that caused me to switch from
master-SNAPSHOT
tomaster
, so I’ll need to keep an eye on it.