christophd opened a new issue, #3449:
URL: https://github.com/apache/camel-k/issues/3449
The Camel K operator tries to resolve dependencies for a given integration
by having a look at the source code of the integration (e.g. by looking at the
used Camel route URIs `from('componentA:foo').to('componentB:bar')`).
In this process the operator tries to resolve the dependency via the given
CamelCatalog.
We should raise build errors when such a dependency is not resolvable with
the given CamelCatalog. At the moment the dependency is left unresolved causing
runtime errors when the integration is running (due to missing artifact in the
runtime classpath).
The integration should be put to error phase as a result.
--
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-unsubscr...@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
