Improve gradle and maven test harness to give us more release confidence

[maxandersen]

Some issues have been discovered after or shortly before a release. And they were related to our Gradle test harness (and Maven too). Especially, the Gradle side is not complete enough to inspire confidence. we need @gsmet to be say 80% confident (you can't reach 100% with this model :D )

Now some needs to figure out a set of concrete actions (list of tests?). We need tis issue to be actionable.
Who will do this @geoand or @maxandersen or ?

[quarkusbot]

/cc @quarkusio/devtools

[emmanuelbernard]

What’s the goal of this issue? I’m not sure continuously do better X brings value as an issue. I must be missing something.

[maxandersen]

you asked for it an issue on improving the test harness to track it. I opened it :)
For me its just about ensuring when we fix issues in mavne/gradle that we keep improving the test harness. Maybe @geoand has a more concrete list of already known "holes" in the testsuite we can add.

[geoand]

We need all sort of Gradle tests TBH. Gradle stuff breaks too much between releases, which wouldn't happen if we had a fair amount of Gradle tests.

[emmanuelbernard]

Thanks, I'll rephrase a bit then.

[geoand]

I would say that currently @aloubyansky is the best person to specify our most pressing areas for improved Gradle testing.

[emmanuelbernard]

I gathered from you recent conversations that this one is "done"

[maxandersen]

@geoand @aloubyansky want to call it done/ok by now as discussed last week or do we have some specific ones we are missing we want to bring attention on ?

[aloubyansky]

I'm fine closing it. However, I don't consider myself being the lead/owner of this component, who actually should be evaluating these issues and doing planning.