Gradle scan and analysis?

[Gerd Aschemann]

Hi Dirk and others,

let's assume I would like to analyze a Gradle project with jQA based on the Gradle Tooling API.

Would it be possible with a jQA plugin? Or would it require hooking into the whole process (jQA framework) very early, e.g., to enable setting respective starting points (classes, etc.) from `build/` instead of `target/` as in the Maven case. 

As far as I can see, I could approach Gradle almost similar to Maven (3), at least for the happy path (having `src/main/java` etc.). Or are there any concerns?

Regards

  Gerd

[dirk.mahler]

Hi Gerd,

I think the integration between Gradle and jQA should be very similiar
to the Maven integration. For Maven the plugin brings the following
benefits over using the CLI:

- dependency resolution to other modules in the same build and external
libraries
- detection of folders containing classes and test reports
- access to the lifecycle of the build system (e.g. for caching the
Neo4j instance and obtaining config values)

I had a quick look at the description of the Gradle Tooling API - it
looks like the same things could be done.
I'm currently on vacations, if you like we could schedule a call next
week to discuss some details.

Cheers

Dirk

Am 2024-04-02 13:05, schrieb 'Gerd Aschemann' via jQAssistant:
> Hi Dirk and others,
>
> let's assume I would like to analyze a Gradle project with jQA based

> on the Gradle Tooling API [1].

>
> Would it be possible with a jQA plugin? Or would it require hooking
> into the whole process (jQA framework) very early, e.g., to enable
> setting respective starting points (classes, etc.) from `build/`
> instead of `target/` as in the Maven case.
>
> As far as I can see, I could approach Gradle almost similar to Maven
> (3), at least for the happy path (having `src/main/java` etc.). Or are
> there any concerns?
>
> Regards
> Gerd
>

> --
> You received this message because you are subscribed to the Google
> Groups "jQAssistant" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jqassistant...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jqassistant/e2a3ae32-e30f-4bb3-976e-6e9b2c2fb92en%40googlegroups.com
> [2].
>
>
> Links:
> ------
> [1]
> https://docs.gradle.org/current/userguide/third_party_integration.html
> [2]
> https://groups.google.com/d/msgid/jqassistant/e2a3ae32-e30f-4bb3-976e-6e9b2c2fb92en%40googlegroups.com?utm_medium=email&utm_source=footer

[Gerd Aschemann]

Oh, meanwhile I found the jQA Gradle Plugin from Jens (could vaguely remember that there was some preliminary work wrt. Gradle). 

Hi Jens,

are you planning to migrate to jQA 2.x? I took a short look into the code and it’s not straight forward as the commandline component has breaking changes. Is there a migration guide, Dirk?

Thanks

  Gerd

--
You received this message because you are subscribed to the Google Groups "jQAssistant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jqassistant...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jqassistant/e2a3ae32-e30f-4bb3-976e-6e9b2c2fb92en%40googlegroups.com.

--

Gerd Aschemann --- Veröffentlichen heißt Verändern (Carmen Thomas)
+49/173/3264070 -- ge...@aschemann.net -- http://www.aschemann.net

[Gerd Aschemann]

Let’s proceed here: https://github.com/kontext-e/jqassistant-gradle-plugin/issues/10

[Gerd Aschemann]

Hi Dirk,

thanks, some mails later I found the existing (but slightly outdated) Gradle plugin from Jens, and can hopefully sort out everything else with him (cf. my GH issue/PR at kontext-e).

Nevertheless I’d be happy to talk to you soon (though next week I’m at JavaLand).

Enjoy your vacation meanwhile 

  Gerd

To view this discussion on the web visit https://groups.google.com/d/msgid/jqassistant/458771f5ae81953075b8809e054167b7%40buschmais.com.