-
Notifications
You must be signed in to change notification settings - Fork 1
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
Incompatible with newer Gradle versions #1
Comments
hi there, i was triggered by the fine article about the ddd-stuff that found its way into jqa and also wanted to use the gradle setup. i think i just read your error message as something that got fixed in kontext-e/jqassistant-gradle-plugin#7 ... but i also think that the persons needed to merge that PR ( @kontext-e ) haven't had found the time to review the PR yet. maybe that could change if @kontext-e gets nudged a bit? 👋 |
Thanks for the hint. The PR indeed fixes what I also tried in my local setup. |
Just merged the request and release version 1.0.1. Tried with Gradle 6.8.3 and 7.1.1, worked for me. Please let me know if you still encounter problems. |
Where is it published? I cannot pull the latest release
|
I double checked there. There seems to be an error during the publish I tracked it down in the gradle-plugin-repo See the duplicate gradle.gradle in the artifact name |
Indeed there is only a 1.0.0-SNAPSHOT. It also has the artifact id de.kontext_e.jqassistant.gradle.gradle.plugin. Apparently this worked for a number of people. |
after reading your conversation i must admit: i did not understand the consequences of your findings. if i may bluntly ask ... does it work now? 😊 //edit: iguessiwilljustcheckitoutandtry. whydoievenask 🤕 |
@dhamann Did it work? @lostiniceland and me got different results... |
I found the culprit. I've accidentally mixed jqa-plugin versions with the git-plugin version from kontext-e
Instead of 1.8.0 I've had "jqaVersion" which resolved to 1.10.0 for which the Git plugin does not exist. Anyway, the error message was kind of misleading. |
i have tried with 7.1.1, had strange results. wanted to confirm by supplying a simple testbed as my own repo (which fails) ... will do that probably sometimes this week but then yesterevening i found out about the examples subproject here ... which does work a bit different ... but which works somehow ... that confused me some more. need to play around and will gladly report afterwards @kontext-e 👍 |
i failed, then got it to work, then failed again ... so let me pre-pose my solution: changing the dependency under plugins to drop failed:using the Usage-Suggestions like adding id "de.kontext_e.jqassistant.gradle" version "1.0.1-SNAPSHOT" to plugins succeeded:adding failed:using the Usage-Suggestions by adding the failure message along the line of:
So ...
I have not much experience around working with mvn snapshots and the way they are resolved vs "notsnapshots" ... is it important for this plugin to rely on a snapshot? what are the advantages vs "notsnapshots"? (actually i just stumbled upon this lack of knowledge on my side when inspecting redhat quarkus way of doing things with snapshots where they somewhere always expect a nonexisting version like 9999 ... which must have something to do with the way maven gav coordinates are resolved. but i need to brush up my knowledge there) |
I am trying to run the plugin with Gradle 7.1.1 (due to Java 16 as preparation for the next LTS 17) and the plugin seems to use deprecated Gradle API.
https://github.com/lostiniceland/mtmd/tree/jqa
Running
./gradlew :backend-quarkus:scan
produces the following outputPlease note, I am using the Kotlin-DSL for Gradle.
The text was updated successfully, but these errors were encountered: