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

Update Dockerfile to use Java 17 #2924

Closed
link2xt opened this issue Jan 17, 2024 · 1 comment · Fixed by #2925
Closed

Update Dockerfile to use Java 17 #2924

link2xt opened this issue Jan 17, 2024 · 1 comment · Fixed by #2925
Assignees
Labels

Comments

@link2xt
Copy link
Contributor

link2xt commented Jan 17, 2024

Nightly builds are using Dockerfile from this repository.

Since #2838 is merged, nightly builds fail with the error:

Welcome to Gradle 8.0.2!

Here are the highlights of this release:
 - Improvements to the Kotlin DSL
 - Fine-grained parallelism from the first build with configuration cache
 - Configurable Gradle user home cache cleanup

For more details see https://docs.gradle.org/8.0.2/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* Where:
Build file '/tmp/build/841c1d7f/build.gradle' line: 2

* What went wrong:
An exception occurred applying plugin request [id: 'com.android.application', version: '8.1.4']
> Failed to apply plugin 'com.android.internal.application'.
   > Android Gradle plugin requires Java 17 to run. You are currently using Java 11.
      Your current JDK is located in /usr/lib/jvm/java-11-openjdk-amd64
      You can try some of the following options:
       - changing the IDE settings.
       - changing the JAVA_HOME environment variable.
       - changing `org.gradle.java.home` in `gradle.properties`.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Dockerfile should be updated to use Java 17.

@adbenitez
Copy link
Member

note: maybe in the future we should use the same for the PRs previews, that way only one place needs to be changed and avoid this situation again

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

Successfully merging a pull request may close this issue.

2 participants