[GitHub] [camel-k] lburgazzoli commented on issue #4024: Make project generation explicit and generic

["lburgazzoli (via GitHub)" <gi...@apache.org>]

lburgazzoli commented on issue #4024:
URL: https://github.com/apache/camel-k/issues/4024#issuecomment-1414438853

   > I am all in for this proposal to have the standard maven project with source code instead of injecting it, sound more natural and allows flexibility in the future to tweak the build tool (mvnd?) I don't know the original motivation to have camel-k-runtime to inject the source code (perhaps, to not depend on the pod operator file system). With this move, there will be less code to maintain in camel-k-runtime.
   
   I really don't read this proposal this way, and if it were then it would break any major camel-k use case as you would need to trigger a build every time a kamelet binding/integration changes.  We had the option to include the sources back in the day and I'm all for supporting this, but it must be an opt in feature.
   
   


-- 
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