Gradle plugin output tracking breaks if quarkus.package.output-directory is configured

[britter]

Describe the bug

The QuarkusBuild task does not provide a way to reconfigure it's output location. Instead it's hardcoded to $buildDir/quarkus-app. At the same time, users can configure the output location by setting the quarkus.package.output-directory. This will cause the build to create the output in a different location. However Gradle is unaware of this location, so UP-TO-DATE checking and build caching breaks because Gradle will track the location returned from QuarkusBuild.getFastJar(). Furthermore it's not possible to easily consume QuarkusBuild output from another task, because QuarkusBuild is unaware of the changed location.

Expected behavior

When changing the output location via quarkus.package.output-directory this should also change the value returned from QuarkusBuild.getFastJar() accordingly. #28896 is related to this.

Actual behavior

Gradle is unaware of changes to QuarkusBuild output location configured by quarkus.package.output-directory

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @glefloch, @quarkusio/devtools

[glefloch]

Thanks for reporting this issue, we need to take care of that variable.

[geoand]

@jacobdotcosta would you be interested in this?

[jacobdotcosta]

Yes, I'll take a look.