Fix few gradle misconfigurations related to gradle plugin tests

[Eng-Fouad]

I am not sure if the misconfigurations here are intended or not.

include ':dependency'
include ':included-quarkus'

dependency does not exist, while included-quarkus exists in a sub module.

cc @snazy

related #38607

[Eng-Fouad]

Also not sure exactly why it worked on pre-gradle 9.0, while it failed on gradle 9.0.

[snazy]

Hm - a Gradle include 'something-that-does-not-exist' is valid and creates an "empty" project (even if it doesn't make much sense). Maybe there's something else.

[Eng-Fouad]

Hm - a Gradle include 'something-that-does-not-exist' is valid and creates an "empty" project (even if it doesn't make much sense). Maybe there's something else.

I think this is a new behavior in Gradle 9.0: gradle/gradle#33184

Also see: https://docs.gradle.org/current/userguide/upgrading_version_8.html#deprecated_missing_project_directory

Starting with version 9.0, Gradle will not run builds if a project directory is missing or read-only

[snazy]

Interesting, that's definitely a new behavior. But yea - why have a Gradle project w/o a directory.

[Eng-Fouad]

cc @geoand

[geoand]

Thanks.

I can't say myself, so let's wait for @snazy

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 2b998f8.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.