Dependency Resolution Failure for SNAPSHOT Versions in Maven Central

[dzuluaga]

We encountered a build failure in our React Native project due to an inability to resolve a Java dependency from Maven Central. The missing dependency was com.openmobilehub.android.auth:plugin-google-non-gms:2.0.0-SNAPSHOT.

Temporary Solution: To bypass this issue, we added the Sonatype staging repository to the project-level build.gradle:

allprojects {
    repositories {
        maven { url 'https://s01.oss.sonatype.org/content/groups/staging' }
        // other repositories
    }
}

This change allowed the project to build by resolving the dependencies from the staging repository instead of Maven Central.

Impact: While this solution works temporarily, it raises concerns about the stability and maintenance of dependencies, especially for production builds. Using dependencies from a staging repository can introduce risks as these versions are not final and might include unfinished features or bugs.

Questions and Actions Needed:

1. Stable Release Timing: When can we expect a stable release version of com.openmobilehub.android.auth:plugin-google-non-gms to be available on Maven Central?
2. Dependency Management: Should we continue using the staging repository for development builds, or do we have alternatives that ensure more stability?
3. Build Configuration: How should we configure our build setup to differentiate between development and production environments concerning repository usage?

[Esemesek]

Hey @dzuluaga, We used snapshot versions, as at the time of Android implementation there was no stable version released. Fixed in preparation for React Native release: https://github.com/openmobilehub/react-native-omh-auth/pull/37.

[dzuluaga]

LGTM. Thanks.