Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the jitpack dependency still available? #5

Closed
jsparidaans opened this issue Feb 28, 2024 · 1 comment
Closed

Is the jitpack dependency still available? #5

jsparidaans opened this issue Feb 28, 2024 · 1 comment

Comments

@jsparidaans
Copy link

jsparidaans commented Feb 28, 2024

Hi! It looks like the jitpack dependency is no longer available, our CI pipeline fails on building this dependency with the following error:

Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find com.github.SmartToolFactory:Compose-Bubble:1.0.0.
Required by:
    project :app

Jitpack itself appears to be up

From the dependency's log on Jitpack, there appears to be an issue with the com.android.tools.build:gradle: version

* What went wrong:
A problem occurred configuring root project 'Compose Speech Bubble'.
> Could not resolve all files for configuration ':classpath'.
   > Could not resolve com.android.tools.build:gradle:7.4.0.
     Required by:
         project : > com.android.application:com.android.application.gradle.plugin:7.4.0
         project : > com.android.library:com.android.library.gradle.plugin:7.4.0
      > No matching variant of com.android.tools.build:gradle:7.4.0 was found. The consumer was configured to find a library for use during runtime, compatible with Java 8, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '8.0-rc-1' but:
          - Variant 'apiElements' capability com.android.tools.build:gradle:7.4.0 declares a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component for use during compile-time, compatible with Java 11 and the consumer needed a component for use during runtime, compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.0-rc-1')
          - Variant 'javadocElements' capability com.android.tools.build:gradle:7.4.0 declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.0-rc-1')
          - Variant 'runtimeElements' capability com.android.tools.build:gradle:7.4.0 declares a library for use during runtime, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component, compatible with Java 11 and the consumer needed a component, compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.0-rc-1')
          - Variant 'sourcesElements' capability com.android.tools.build:gradle:7.4.0 declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.0-rc-1')

I think creating a new tag and releasing a v1.0.1 should resolve these issues

Thanks in advance!

@Brammos
Copy link
Contributor

Brammos commented Feb 28, 2024

fixed it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants