ppalaga commented on pull request #2661:
URL: https://github.com/apache/camel-quarkus/pull/2661#issuecomment-848563591
> @ppalaga how do you want to handle this? This would remove remove the
broken `qute.json` from the catalog. Is there a simple means of getting a
correct JSON file included?
I am still striving to understand what's wrong with qute.json from Camel K
perspective. `javaType` being `org.apache.camel.component.qute.QuteComponent`
is correct from CQ's point of view. The type exists in
`org.apache.camel.quarkus:camel-quarkus-qute-component`. My working hypothesis
is that Camel K does some wrong assumption about where to find that class
(maybe it thinks it is in `org.apache.camel:camel-qute` which does not exist
apparently). And that's why I say we should check/fix what we output to
`metadata: {camelArtifact: }` of `qute.json` so that Camel K has an
authoritative source for the Maven coordinates under which the `javaType` is
supposed to exist.
I am all for clarifying this.
Removing `qute.json` from CQ catalog would not be correct. The extension and
component exist and we support it. Removal would impact a couple of our tools
that utilize the info from the catalog.
--
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]
