groupie: com.xwray:groupie-viewbinding can't be resolved

You can add a bintray repository for now. As it’s a new module, I assume it may take some time before it is synced to jCenter.

repositories {
  maven { url 'https://dl.bintray.com/lisawray/maven' }
}

Using JitPack sounds good because we can also resolve #315 without any additional work.

The latest version of all modules are already available in JitPack:

allprojects {
  repositories {
    maven { url "https://jitpack.io" }
  }
}

dependencies {
  implementation "com.github.lisawray.groupie:groupie:2.8.0"
  implementation "com.github.lisawray.groupie:groupie-databinding:2.8.0"
  implementation "com.github.lisawray.groupie:groupie-viewbinding:2.8.0"
  implementation "com.github.lisawray.groupie:groupie-kotlin-android-extensions:2.8.0"
}

@zsoltvilagos If you use JitPack, the group id changes to com.github.lisawray.groupie. See the comment right above yours.

It seems that groupie-viewbinding is not linked to JCenter although auto-syncing is enabled in jcenter/bintray.gradle.

• https://bintray.com/lisawray/maven/groupie-viewbinding
• https://reflectoring.io/bintray-jcenter-maven-central/#publish-to-jcenter

I’m not sure what happened, but maybe this time we have to link the artifact to JCenter manually.

This should be fixed now.

If enabling JCenter syncing is not possible in the near future, adding the guide to add the Bintray repository url to the README as @yshrsmz answered is desirable: https://github.com/lisawray/groupie/issues/333#issuecomment-607079271.

Thank you @yshrsmz for answering. I’ll keep this issue open for a while longer - if no one mentions it in a few days I’ll close it.

maybe it’s time to fork the repo and create a new org

❓ Would it be possible to somehow move forward with this problem? Currently blocks me to do an update in my project.