squakez commented on PR #5039: URL: https://github.com/apache/camel-k/pull/5039#issuecomment-1882662420
Thanks for putting this experiment together. I think an effort like this makes sense only if integrated in other Camel tooling, ie, Camel JBang. It makes sense both from a design and maintenance point of view. We have already a `camel dependency list` command which we should leverage/enhance instead of reinventing the wheel. What I suggest is to have that command reliable enough and possible also work independently from the runtime chosen. Ideally, the same should be able to expose `capabilities` besides dependencies which I think this draft work does not cover. > I tried to use camel dependency list but it is a bit complex to have it running in an offlline mode, it was 2s slower too, as it creates a maven project, then export it. What we maybe need then is a development that makes that command to just list the project dependencies required on a generated project. Once that is ready, then, the operator can just use it to calculate the dependencies and capabilities of a source or, more in general, a project. I wonder if some of the development you've done here can be already reused on Camel JBang. -- 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
