Closed DirkMahler closed 1 year ago
We are aware of this issue. And hopefully we can start after 1.6.0 with it.
The blog post is outdated, see https://github.com/buschmais/jqa-maven-plugin/issues/17#issuecomment-427828321.
I started writing a jqa-gradle-plugin. It is not finished yet and I did not post the WIP-state, but I hold this: https://github.com/simonnagl/jqa-gradle-plugin
I tried to keep it simple and just call the command line wrapper and not use the jqa java api, which the maven plugin does. If you want this project name or like to see my state, just tell me.
@Skyr is also on this one (https://github.com/Skyr/jqassistant-gradle-plugin)
Thanks for mentioning me :-) @simonnagl please have a glance at my efforts. Perhaps we can work on it together. The current state is that all the initiialization of JQAssistant should be there. Next step would be starting the actual parsing (my guess is that this shouldn"t be so hard). After that, it would be nice to translate some data of the Gradle build to JQAssistant data structures... but first things first :-)
@Skyr Wasn't aware of that. If any support needed from our side please let us know!
@simonnagl please have a glance at my efforts. Perhaps we can work on it together. The current state is that all the initiialization of JQAssistant should be there.
I just checked your code. You took the approach of using the jqAssistant java API and not running the command line wrapper. I hopefully have time to review my current state this weekend and push my changes. It would be motivating to work together on this. After you have seen my state we can discuss how to continue.
Maybe @jensnerche is as well interested in this topic?
It seems that both @simonnagl and @Skyr didn't go on with Gradle plugin development. So I started an attempt as well. See https://github.com/kontext-e/jqassistant-gradle-plugin what already works and how to use it.
Hi @kontext-e, could you imagine to continue your work on the Gradle plugin as part of jQAssistant distribution?
@obfischer Given the fact that I/we already sponsored the command line version, it's not completely out of scope. ;)
@kontext-e, thank you for publishing your work. I deleted my repository.
I started working on updating the plugin to run with Gradle 7. It looks like there will be breaking changes, meaning that the plugin will then not run with older Gradle versions anymore. I am proposing a 2.0 to not force anyone to upgrade his build.
@lostiniceland If you need support on this topic (from jQA side and based on the experiences with Maven/CLI) please let us know!
I have been made aware of a PR which already addressed the Gradle API changes for the plugin. https://github.com/kontext-e/jqassistant-gradle-plugin/pull/7 It also fixes a chicken-egg problem the plugin-repo has. It just needs approval
Closing this as the Kontext-e plugin is currently the way to go.
I followed this blog post to integrate jqassistant into a gradle project http://techblog.kontext-e.de/jqassistant-with-gradle/
It explains every necessary step and provides a copy and paste solution. I should be a good baseline to create an official gradle plugin.