-
Notifications
You must be signed in to change notification settings - Fork 1
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
Have Quarkus buildpack set env variable to ensure executable-jar buildpack picks the correct JAR #12
Comments
OK, can you try the following build command?
alternatively for native-image builds...
When you use the |
@sebastiangraf have you tried what @dmikusa suggested? Has it worked? |
I followed your suggestion @dmikusa with:
and I ended up with:
|
Can you include the output of It looks like it is building and running some command, but that command is failing and complaining about the arguments. It would also be helpful to get the full build log. |
no problem.
I have removed the thousdans of
|
Sorry for the delayed response. Is
There is an issue to make the JAR it picks more configurable, but that's not been implemented yet. http://github.com/paketo-buildpacks/executable-jar/issues/206. |
Yeah, that was probably it; it picked a random jar with a declared once paketo-buildpacks/executable-jar#206 is fixed I suggest this issue becomes about having |
When building the Sample Project located under https://github.com/paketo-buildpacks/samples/tree/main/java/native-image/quarkus-native with a local copy of this buildpack, the resulting image is not executable. The same applies for a more recent version of quarkus and jvm.
Expected Behavior
Checking out this repository under
/tmp/quarkus
and invoked viaResult would be an image
test-image
that would be directly executable. When the image runs, something likeshould occur.
Current Behavior
Build runs, but is not compiling anything
Executing this image results in
I guess that invoking the quarkus buildpack is not including the java buildpack as no compilation takes place.
Possible Solution
Including the quarkus buildpack directly int he java buildpack might solve the problem.
Steps to Reproduce
Motivations
I try to build a quarkus app with the help of buildpacks :)
The text was updated successfully, but these errors were encountered: