-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native test fails if quarkus.package.output-directory
is configured differently
#28131
Comments
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 23, 2022
gsmet
added a commit
that referenced
this issue
Sep 26, 2022
Take quarkus.package.output-directory into account when launching native tests
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Oct 3, 2022
…ive tests Fixes: quarkusio#28131 (cherry picked from commit a8c0aee)
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If you leave the property
native.image.path
empty, the path is guessed by the system. Though it is always guessed in the default output location. If thequarkus.package.output-directory
is changed (for example in the context of a ci pipeline), the native image can not be found.Expected behavior
If
native.image.path
is not defined andquarkus.package.output-directory
is defined to output to a non-default directory. Thennative.image.path
should be guessed inside of the definedquarkus.package.output-directory
.Actual behavior
The
native.image.path
is always guessed in the default output location.How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.12.3.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: