You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In examples instructions, there is for example: ./target/sw-quarkus-greeting-{version}-runner instead of ./target/serverless-workflow-greeting-quarkus-runner command.
Acceptance criteria
The version is removed from all native image execution commands in all serverless-workflow-examples.
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
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
LuboTerifaj
changed the title
Wrong command for native image execution in Greeting Example
Wrong command for native image execution in serverless-workflow-examples
Jun 11, 2024
Describe the bug
Wrong command for native image execution in serverless-workflow-examples.
Details
In examples instructions, there is for example:
./target/sw-quarkus-greeting-{version}-runner
instead of./target/serverless-workflow-greeting-quarkus-runner
command.Acceptance criteria
The version is removed from all native image execution commands in all serverless-workflow-examples.
Expected behavior
No response
Actual behavior
No response
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
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
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: