[
https://issues.apache.org/jira/browse/CAMEL-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876641#comment-17876641
]
Aurélien Pupier commented on CAMEL-21104:
-----------------------------------------
example of classical flow:
* camel init my-route.camel.yaml
* Experiment locally
* share changes via git push
* experiment potentially more and git push more modifications
* project ready to go to "productization" step, camel export
* git push the Maven project
--> currently the file my-route.camel.yaml will be duplicated. it will be both
at the root of repository and inside src/main/resources
The expected behavior is to remove the my-route.camel.yaml file which is at the
root of repository. So to do a move instead of a copy.
I think we need to keep the files when exporting to a completely different
folder.
> camel-jbang - Delete used files when creating a Camel project "in-place" with
> Camel JBang
> ------------------------------------------------------------------------------------------
>
> Key: CAMEL-21104
> URL: https://issues.apache.org/jira/browse/CAMEL-21104
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Aurélien Pupier
> Priority: Minor
>
> currently when creating a Camel project , the used files are copied to th
> enew project;
> When it is exported to another folder that sounds fine but when creating
> in-place, the files sounds as duplicated.
> it will facilitate this important use case:
> - create standalone camel file(s)
> - push them on a git repository
> - evolve these routes
> - migrate to a Maven project and stay in the same repository
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
