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

gradle version mismatch #3796

Closed
himanshu-mind opened this issue Mar 29, 2019 · 13 comments
Closed

gradle version mismatch #3796

himanshu-mind opened this issue Mar 29, 2019 · 13 comments
Labels

Comments

@himanshu-mind
Copy link

Jitpack is using Gradle 4.8.1

which is giving following error:

Failed to apply plugin [id 'com.android.library']
Minimum supported Gradle version is 4.10.1. Current version is 4.8.1. If using the gradle wrapper, try editing the distributionUrl in /home/jitpack/build/gradle/wrapper/gradle-wrapper.properties to gradle-4.10.1-all.zip

@Sergioct
Copy link

Sergioct commented Apr 9, 2019

Same error here

@dhiyaulhaqZA
Copy link

Me too

Minimum supported Gradle version is 4.10.1. Current version is 4.8.1. If using the gradle wrapper, try editing the distributionUrl in /home/jitpack/build/gradle/wrapper/gradle-wrapper.properties to gradle-4.10.1-all.zip

@kyeonghwan-kong
Copy link

Me too

@kyeonghwan-kong
Copy link

kyeonghwan-kong commented May 2, 2019

I was developing Android, and I fixed it by modifying as below.

buildscript {
     ...
     dependencies {
        classpath 'com.android.tools.build:gradle:3.2.0'
        ...
     }
     ...
}

If set to com.android.tools.build:gradle:3.4.0, the minimum Gradle version is 5.1.1.

@wintonBy
Copy link

Anybody has solve this problem?

@Sergioct
Copy link

Sergioct commented Oct 1, 2019

I couldn´t resolve it. I have changed to another repository web.

@zhanzengyu
Copy link

I was developing Android, and I fixed it by modifying as below.

buildscript {
     ...
     dependencies {
        classpath 'com.android.tools.build:gradle:3.2.0'
        ...
     }
     ...
}

If set to com.android.tools.build:gradle:3.4.0, the minimum Gradle version is 5.1.1.

Thanks. I solve it.

@andob
Copy link

andob commented Apr 29, 2020

Current version of Gradle Gradle 4.8.1 is not compatible with Kotlin plugin.
Please use Gradle Gradle 4.9 or newer or previous version of Kotlin plugin.

This is getting serious.

Could you PLEASE modify jitpack's gradle wrapper settings, so that it will read the properties from

project root/gradle/wrapper/gradle-wrapper.properties

and not

/home/jitpack/build/gradle/wrapper/gradle-wrapper.properties

?

Ever since I started using jitpack, I always had to use outdated versions... Using outdated versions is not a solution, but a hack...

EDIT (aug 2020): I'm not using JitPack anymore. I switched to my own hosted maven repo (using Apache Archiva). Never looked back, now I got so much control.

@hykilpikonna
Copy link

hykilpikonna commented May 23, 2020

@andob
I had the same problem too, but I realized that I put *.jar in my .gitignore. After removing it from the ignore list and committing gradle-wrapper.jar into the repo, Jitpack worked as expected.

WARNING: gradle/wrapper/gradle-wrapper.jar does not exist! Needs to be committed.

hykilpikonna added a commit to HyDevelop/OsuBeatmapStudio that referenced this issue May 23, 2020
@mspnr
Copy link

mspnr commented Aug 26, 2020

Actually jitpack can use your own Gradle version. E.g. here I used version 6.5 and it worked just fine.

What I was missing is the file ./gradlew, which I initially didn't submitted to github. Yes, you should remove it from .gitignore and upload it to github.
This is also mentioned in https://jitpack.io/docs/ANDROID/ , but not very clear. ./gradlew also present in the example https://github.com/jitpack/android-example.

See #2311 , it was very helpful.

@wukuiqing49
Copy link

Me too!!

@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Sep 28, 2022
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

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

No branches or pull requests

10 participants