-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Exception occurred applying plugin request "de.gurkenlabs.semverguru" #818
Comments
Thank you for your reporting your first LITIENGINE issue! We are looking forward to your further contributions. |
This issue was resolved a while back (I think) and de.gurkenlabs.semverguru should be at version 1.4. The workaround I found was downloading the project from the parent repo and pushing that to your forked repo. This should resolve all of your issues. |
@iamllcoolray Thank you for your quick response. I am not sure I understand the term of "parent repo". I am using command "git clone https://github.com/gurkenlabs/litiengine.git" to clone the repo. |
Since your clone is using Gradle 8.5 and SemVerGuru 1.3, you have not checked out the most recent revision of LITIENGINE (which is at Gradle 8.7 and SemVerGuru 1.4). |
@jianh73 oh what I meant about parent/child repo:
Similar IssuePossible SolutionTry downloading the zip itself. I think that's what I did a while back and it worked (this was back in December or January). but it should also work when you fork the repository as well. See Also |
Describe the bug
When I try to build 0.8.0, I got error message "An exception occurred applying plugin request [id: 'de.gurkenlabs.semverguru', version: '1.3']
Stack Trace
Build file '/Users/jian/Documents/projects/litiengineprojects/litiengine/build.gradle' line: 1
An exception occurred applying plugin request [id: 'de.gurkenlabs.semverguru', version: '1.3']
To Reproduce
I am using IntelliJ CE 2030.3.6 on Mac
Gradle 8.5
java 21.0.2
Thanks for any suggestion!
Your System:
I am using IntelliJ CE 2030.3.6 on Mac
Gradle 8.5
java 21.0.2
The text was updated successfully, but these errors were encountered: