Fix test in sample gradle projects

[glefloch]

This branch fix sample gradle projects used by integration-test.
I also added an assertion on the command result to make sure we detect this ASAP, even if logs are off.

Also, this config injection works in dev mode, but fails on test. As these tests are only testing add/remove extension, I simply removed the property injection. @geoand is a normal behaviour?

@ConfigProperty(name = "quarkus.application.version")
String appVersion;

close #14799

[geoand]

Also, this config injection works in dev mode, but fails on test. As these tests are only testing add/remove extension, I simply removed the property injection. @geoand is a normal behaviour?

Yes, it's expected to not work in test mode.
So go ahead and remove the property from those tests

[geoand]

Thanks 👍

[aloubyansky]

Why are those properties expected not to be available in tests?

[geoand]

Because they are pulled from Maven or Gradle and in tests we can't reliably obtain that information

[aloubyansky]

The name and the version? Unless the props are explicitly set by the user they are initialized to the runner module's artifactId and version.

[geoand]

Yeah, but in the tests that does not work properly AFAIR

[aloubyansky]

The project's artifactId/name and version? If we didn't have that info we wouldn't be able to resolve dependencies and set up the classpath.

[geoand]

Then I guess we are just missing so glue code to make it work for tests as well :)

[aloubyansky]

Thanks @glefloch