astefanutti commented on pull request #1816: URL: https://github.com/apache/camel-k/pull/1816#issuecomment-763896401
Damn, I'm not sure what's going on in my brain, but it seems it cannot get that `kamel inspect` does not retrieve details about the Integration resource from the cluster :(. Maybe I think of it as being somewhat related to `kubectl describe`, and I found it counter intuitive that running `kamel inspect` would create a Maven project and run `quarkus-maven-plugin`. For the complexity of a possible `kamel local build`, I don't see it as much more complex as the current proposition. Actually, the current implementation calls the `ComputeQuarkusDependenciesCommon` method, which is what the `computeQuarkusDependencies` builder task does. I see the `kamel local build` as a way of calling the builder locally, like `kamel local build --task=ComputeQuarkusDependencies`, as a way to replicate what the builder does, that is executing a sequence of tasks. It would run locally, using the local environment, which the `local` semantic makes explicit as opposed to `kamel inspect`, with the same benefit, but more evolutive, of reusing existing builder tasks. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
