[
https://issues.apache.org/jira/browse/CAMEL-17345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463066#comment-17463066
]
Claus Ibsen commented on CAMEL-17345:
-------------------------------------
Yes overkill, we should just generate files for a camel-quarkus project as that
is what camel-k is using.
Using a template engine is okay. But I think we only need to generate a pom.xml
file,
and then move the source into src/main/java or src/main/resources.
And if so then maybe a template engine is also a bit overkill, as the dynamic
part of the pom.xml is only the dependency section.
However we can use freemarker and then just add camel-freemarker to
camel-kamelet-main where we have other set of needed dependencies for running
with jbang, that is okay.
> camel-jbang - Add command to create as a maven project
> ------------------------------------------------------
>
> Key: CAMEL-17345
> URL: https://issues.apache.org/jira/browse/CAMEL-17345
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 3.15.0
>
>
> Add a new create-project command that would setup what you would "run" as a
> maven project with a pom.xml file, and source files in src/main/resources and
> src/main/java - and a log4j.properties file etc, so you can start with jbang
> and quickly hack/try something and run that, etc and then continue this as a
> regular maven project.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
