andreaTP commented on PR #3994:
URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1400647390
Updated the PR using a `pom.xml` and a configuration closer to
`camel-k-runtimes`, I do believe that you want to review the artifact name and
the version used.
Let me know how thi
andreaTP commented on PR #3994:
URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1400451274
> Count on it. I think the very first thing is to have a distribution pom
with the same configuration of the camel-k-runtime. When we run the push action
we'll simply leverage a couple o
andreaTP commented on PR #3994:
URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1400178511
Hi @squakez , thanks for bearing with me!
> So, this is not really going to replace the dependency in a repo, but
instead would create one on demand when it's requested by the user
andreaTP commented on PR #3994:
URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1398477467
> who is going to consume such new configurations
Here we are publishing standard Java Artifacts (i.e. a `jar` file and
additional metadata) not configuration.
Users that want t
andreaTP commented on PR #3994:
URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1398211837
@squakez Sure, sorry for the missing context, here the ultimate goal is to
provide the users a Java library to easily interact with typed Camel-K Custom
Resources using the `fabric8` `ku
