You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/11/01 07:51:50 UTC
[GitHub] [camel-k] tadayosi opened a new issue, #3790: Deprecate overlapping Kamel CLI features in favour of Camel JBang
tadayosi opened a new issue, #3790:
URL: https://github.com/apache/camel-k/issues/3790
There are overlapping features between Camel K `kamel` CLI and [Camel JBang](https://camel.apache.org/manual/camel-jbang.html). To name a few:
* `kamel init` vs `camel init`
* `kamel local run` vs `camel run`
* `kamel bind` vs `camel bind`
We should favour `camel` over `kamel` for the overlapping features and drop them from `kamel` for Camel K 2.0. For now, we should mark them as deprecated.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3790: Deprecate overlapping Kamel CLI features in favour of Camel JBang
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3790:
URL: https://github.com/apache/camel-k/issues/3790#issuecomment-1327145272
Ah cool. `camel dependencies --main-class <file name without extension>` does the trick!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3790: Deprecate overlapping Kamel CLI features in favour of Camel JBang
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3790:
URL: https://github.com/apache/camel-k/issues/3790#issuecomment-1327098902
Thanks! Yes, I agree that `camel bind` cannot replace `kamel bind`.
For `kamel local`, we can deprecate all the commands for sure.
For `kamel local inspect`, I personally find it useful when debugging to see the expected dependencies are actually there. I would contribute the same feature to `camel` CLI, and/or move the same command to `kamel` top-level like `kamel inspect` as a debugging option for developers.
The reason why I'd think the subcommand is useful for debugging is that it uses the same internal mechanism with `kamel run` for resolving dependencies from integration files so it could be used as a fast check on whether expected dependencies are detected without uploading to cloud.
Different views are also welcome.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3790: Deprecate overlapping Kamel CLI features in favour of Camel JBang
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3790:
URL: https://github.com/apache/camel-k/issues/3790#issuecomment-1326340983
I've added a PR that will address this issue. However, I have some remarks.
1. The `kamel bind` cannot be deprecated because we also take care of deploying the `KameletBinding` and we do much more advanced configuration than `camel bind`.
2. I've deprecated the entire `kamel local`. I am not entirely sure if the `kamel local build` or `kamel local inspect` are actually used by anyone.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] davsclaus commented on issue #3790: Deprecate overlapping Kamel CLI features in favour of Camel JBang
Posted by GitBox <gi...@apache.org>.
davsclaus commented on issue #3790:
URL: https://github.com/apache/camel-k/issues/3790#issuecomment-1327137294
You can use `camel dependencies` to see which dependencies are in use
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3790: Deprecate overlapping Kamel CLI features in favour of Camel JBang
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3790:
URL: https://github.com/apache/camel-k/issues/3790#issuecomment-1299865862
In general I'm in favor to go in that direction. However, for `kamel bind` I think it may be a bit more complicated because it creates and deploy the Integration. It also manages aspects like traits, properties and tenancy operator to use, so, until there is a complete overlap of the command, I'd avoid to mark it as deprecated.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez closed issue #3790: Deprecate overlapping Kamel CLI features in favour of Camel JBang
Posted by GitBox <gi...@apache.org>.
squakez closed issue #3790: Deprecate overlapping Kamel CLI features in favour of Camel JBang
URL: https://github.com/apache/camel-k/issues/3790
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org