Claus Ibsen created CAMEL-23973:
-----------------------------------
Summary: camel export: add --parent-pom option to set parent POM
in exported project
Key: CAMEL-23973
URL: https://issues.apache.org/jira/browse/CAMEL-23973
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
When teams scale up from prototyping with Camel JBang to production
Quarkus/Maven projects, they typically use a parent POM to standardize required
extensions, plugin versions, naming conventions, and common dependencies across
multiple integrations.
Currently, after *camel export*, users must manually edit the generated pom.xml
to add a parent POM declaration. A *--parent-pom* option on *camel export*
would allow specifying this in one step.
Example usage:
{code}
camel export --runtime=quarkus --parent-pom=com.ourorg:camel-parent:1.0 ...
{code}
This would generate the *<parent>* block in the exported pom.xml:
{code:xml}
<parent>
<groupId>com.ourorg</groupId>
<artifactId>camel-parent</artifactId>
<version>1.0</version>
</parent>
{code}
This addresses a common scaling pattern where organizations run many Camel
integrations and need consistent project structure without wrapper scripts or
post-export patching.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
