Skip to content

quarkus-artifact.properties generation is brittle #53209

@oehme

Description

@oehme

Describe the bug

AugmentActionImpl is hardcoded to fetch the path from artifactResultBuildItems.size() - 2. This may or may not be the correct path, depending on how many artifact results have been registered during the build.

This should be a more defensive:

  • Don' hardcode -2
  • Instead, iterate through the list and find one that actually has a path
  • If there are multiple, fail and print which ones are conflicting
  • If there are none, fail as well, as this really shouldn't happen

We currently have a project where no path is generated, which means that quarkus.test.integration-test-artifact-type=jar doesn't work. But it's hard to figure out what's causing the problem, since the missing path is just silenty ignored by AugmentActionImpl

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions