Gradle quarkusDev not working on multiprojects when jandex is present

[Malandril]

Fixes #48637 by avoiding adding a mustRunAfter accross build projects

[aloubyansky]

@Malandril thanks a lot for the fix! It'd be great to include your reproducer as a test though to make sure we don't break it in the future. Would you like to do that?

Our current framework for these kinds of tests assumes there is one (possibly multi) project, which isn't exactly your case. But it should be doable.
Just in case, here is an example test https://github.com/quarkusio/quarkus/blob/main/integration-tests/gradle/src/test/java/io/quarkus/gradle/devmode/BasicJavaApplicationModuleDevModeTest.java
and a test project https://github.com/quarkusio/quarkus/tree/main/integration-tests/gradle/src/main/resources/basic-java-application-project

Let me know in case you want to give it a try. Otherwise, I'll look into it. Thanks!

[Malandril]

@aloubyansky i'll look into i'll try to strip down the reproducer to the minimum

[aloubyansky]

That'd be awesome @Malandril.
Test projects are copied and "augmented" with the relevant Quarkus properties here https://github.com/quarkusio/quarkus/blob/main/integration-tests/gradle/src/test/java/io/quarkus/gradle/QuarkusGradleTestBase.java#L21
This is where the assumption there is only one project is.
In your case, I was thinking we could simply call it directly for each project and then build one with https://github.com/quarkusio/quarkus/blob/main/integration-tests/gradle/src/test/java/io/quarkus/gradle/QuarkusGradleWrapperTestBase.java#L51

And then test dev mode in the main one.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 345841b.

✅ 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.