uber / uber/RIBs

Can't generate RIBs plugin because of Java Version error

Open
#512 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Android
Dominant language
Kotlin
Stars
7.9k
Forks
914
PR merge metrics
No merged PRs in 30d

Description

I was trying to generate the RIBs plugin manually because the one in the InteliJ plugin store and the one referenced in the docs are broken on Android Studio and InteliJ compatible only. I followed the steps in the wiki but got the following error:

A problem occurred configuring project ':tooling:rib-intellij-plugin'.
Could not resolve all artifacts for configuration ':tooling:rib-intellij-plugin:classpath'.
Could not resolve org.jetbrains.intellij.plugins:gradle-intellij-plugin:1.5.3.
Required by:
project :tooling:rib-intellij-plugin
> No matching variant of org.jetbrains.intellij.plugins:gradle-intellij-plugin:1.5.3 was found. The consumer was configured to find a runtime of a library compatible with Java 8, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.2' but:
- Variant 'apiElements' capability org.jetbrains.intellij.plugins:gradle-intellij-plugin:1.5.3 declares a library, packaged as a jar, and its dependencies declared externally:
- Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
- Other compatible attribute:
- Doesn't say anything about org.gradle.plugin.api-version (required '7.2')
- Variant 'runtimeElements' capability org.jetbrains.intellij.plugins:gradle-intellij-plugin:1.5.3 declares a runtime of a library, 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 '7.2')

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Android Tooling wiki instructions and the tooling/rib-intellij-plugin Gradle project named in the error. Reproduce the build and inspect its Java and Gradle plugin compatibility; done means the RIBs IntelliJ plugin can be generated successfully using the documented steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, kotlin
Domain
build-system, devtools, mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.