Open
Description
Dependency Resolution Issue: frag-nav
Background: On August 15, 2024, Jcenter was officially sunset, redirecting all its content to MavenCentral. However, the following dependency is not available on MavenCentral and cannot be resolved:
- classpath "de.mannodermaus.gradle.plugins:android-junit5:1.3.1.1"
- (maybe more)
Details:
- Jcenter Sunset
The sunsetting of Jcenter has caused issues with dependency resolution, as it now redirects to MavenCentral where some dependencies, like the one mentioned above, are not hosted.
Official announcement: Jcenter Sunset - JFrog. - Jitpack.io Issues
As a potential workaround, I explored using Jitpack.io. Unfortunately, Jitpack.io builds dependencies on-demand. This makes it unreliable for resolving the frag-nav dependency because of the mentioned jcenter redirect.
Reference: Jitpack Building. Failed to resolve: com.ncapdevi:frag-nav:3.2.0 jcenter error #252 and @eggplants comment in this issue. - Gradle Caching Masking the Issue
The issue was initially discovered during the setup of a new development environment. The problem did not manifest for my co-workers due to Gradle's caching mechanism, which retained the dependency locally. Even after invalidating caches in Android Studio, the issue persists on a fresh setup because the required dependency is no longer resolvable.
Proposed Next Steps
I'm open to working on resolving this issue, but the repository appears to have been inactive for a few years. Given this, I’m wondering whether you, @ncapdevi, or other maintainers would suggest a long-term solution or have any input on the best course of action.
I wanna made this insights available for everyone because as seen in the repository there are still people using frag-nav
Any guidance or suggestions would be appreciated!
Metadata
Metadata
Assignees
Labels
No labels