Joao Ferr created CAMEL-21983:
---------------------------------
Summary: Camel jbang quarkus produces an incorrect
application.properties file when referring kamelet files
Key: CAMEL-21983
URL: https://issues.apache.org/jira/browse/CAMEL-21983
Project: Camel
Issue Type: Bug
Components: camel-jbang
Affects Versions: 4.11.0
Reporter: Joao Ferr
Attachments: Update_camel_jbang_quarkus_export_logic.patch
As part of the camel jbang export logic, any kamelet and route files are passed
into the resources folder, and these filenames are then referenced in the
output {{application.properties}} file, on properties:
{{quarkus.native.resources.includes}} and
{{{}camel.main.routes-include-pattern{}}}.
Also, this export logic saves {{*.kamelet.yaml}} files in folder
{{.export/src/main/resources/kamelets}} and {{*.camel.yaml}} files in folder
{{{}.export/src/main/resources/camel{}}}.
However, the resulting {{application.properties}} file does not distinguish
between those two file types and declares both kamelet files and route files
locations under {{{}.export/src/main/resources/camel{}}}, leading to kamelet
files not being recognized when the Quarkus application launches.
I've created a patch file for my suggested change on this issue; it's attached
to the ticket.
----
*Additional notes regarding the test environment:*
I'm using the Visual Studio code Karavan plugin to create my application, as
well as my integration files (routes and kamelets). I'm also using the export
functionality that's defined there, via jbang command:
{code:java}
jbang "-Dcamel.jbang.version=4.11.0" camel@apache/camel export --fresh
--directory=/Users/a/integrations/my-integration/.export
--local-kamelet-dir=/Users/a/integrations {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
