davsclaus commented on pull request #6583: URL: https://github.com/apache/camel/pull/6583#issuecomment-999605544
> > we should make the dependency resolution smarter... > > I see, I'm probably missing something here, but camel-jbang by default already import some dependencies, like `camel-platform-http-vertx`, but if an user wants to use kafka for example, kafka jar should be added to classpath via `jbang --cp /path/to/camel-kafka.jar ...`, in order to work with quarkus, all the default dependencies + classpath ones should be parsed and "converted" to the camel-quarkus respective ones? Yes but lets tackle this in another ticket/PR. The idea with jbang run / create-project is that a entry level users to Camel can start with this (and via karavan) and then quickly prototype an integration, and then after a while, take it to the next level and migrate it as a java based camel quarkus project, where we setup all the boilerplate project files for the user. Then the user can continue to load this in the java editor and continue development with more power. -- 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-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
