You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Salvatore Mongiardo (Jira)" <ji...@apache.org> on 2026/03/05 22:32:00 UTC
[jira] [Created] (CAMEL-23137) camel-jbang - Export loses application.properties when source files use Maven project layout
Salvatore Mongiardo created CAMEL-23137:
-------------------------------------------
Summary: camel-jbang - Export loses application.properties when source files use Maven project layout
Key: CAMEL-23137
URL: https://issues.apache.org/jira/browse/CAMEL-23137
Project: Camel
Issue Type: Bug
Components: camel-jbang
Affects Versions: 4.19.0
Reporter: Salvatore Mongiardo
When exporting a Camel application using {{{}camel export{}}}, the {{application.properties}} file content is silently lost if the source project uses the standard Maven project layout ({{{}src/main/resources/application.properties{}}}) instead of having it at the project root.
This affects all runtimes: Spring Boot, Quarkus, and Camel Main.
*How to reproduce:*
Given a project with the following structure:
{code:java}
project/
├── src/main/resources/
│ ├── application.properties <-- contains configuration
│ └── qdrant-rag.yaml
{code}
Running:
{code:java}
camel export \
--runtime=quarkus \
--gav=org.apache.camel.example:qdrant-rag-quarkus:1.0.0 \
--directory=./export-quarkus-test \
src/main/resources/qdrant-rag.yaml
{code}
The export completes successfully (no errors), but the exported {{application.properties}} is {*}empty{*}. All configuration is silently lost.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)