mertdotcc commented on issue #4124: URL: https://github.com/apache/camel-k/issues/4124#issuecomment-1477000023
> The only kind of workaround you can try to adopt at this stage is to try embedding all your dependency source into the same Java class you're using for your Integration (it may be difficult if it's a lot of code, I know). Unfortunately, this is not a possibility for me as we already have a large codebase with many dependencies. Embedding all said dependencies into the same Java class sounds like a nightmare. 🥲 I've read the discussion in the [#4024](https://github.com/apache/camel-k/issues/4024) that you posted and although I am personally super pumped for the changes/additions that are planned for Camel-K V2, I would like to explore the options that I have atm. Do you see any potential workarounds that don't involve having all my dependencies in one single Java class? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
