squakez commented on issue #1656:
URL: https://github.com/apache/camel-k/issues/1656#issuecomment-1477537959
So, what you're trying to do is to unmarshal what the "build" has provided
before. IMO we could avoid that step and instead change the configuration
structure on the directory files.
squakez commented on issue #1656:
URL: https://github.com/apache/camel-k/issues/1656#issuecomment-1477500956
@gansheer I don't have the full historical context to answer, but from what
I've experimented in the past, the best approach is to go in iterations and
make live past and new approac
squakez commented on issue #1656:
URL: https://github.com/apache/camel-k/issues/1656#issuecomment-1431138966
Great analysis. I think that eventually JIB and JKube may coexist if we
manage to have enough resources to support both. For the time being we could
start with JIB implementation IMO
squakez commented on issue #1656:
URL: https://github.com/apache/camel-k/issues/1656#issuecomment-1413648033
Something else we want to consider is to support multi-architecture via JIB:
see #1238
--
This is an automated message from the Apache Git Service.
To respond to the message, pleas
squakez commented on issue #1656:
URL: https://github.com/apache/camel-k/issues/1656#issuecomment-1147180848
Would it make sense to target for a 2.0 version? It looks like we won't be
able to maintain compatibility (at least, not that easily) if we switch to
something new.
--
This is an
