You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/07/14 09:39:29 UTC
[GitHub] [camel-k] christophd opened a new issue, #3449: Raise error when dependency could not be resolved via CamelCatalog
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3449: Raise error when dependency could not be resolved via CamelCatalog
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3449:
URL: https://github.com/apache/camel-k/issues/3449#issuecomment-1241516458
@claudio4j FYI there is `kamel local inspect <integration-file>` that does similar check but locally.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi closed issue #3449: Raise error when dependency could not be resolved via CamelCatalog
Posted by GitBox <gi...@apache.org>.
tadayosi closed issue #3449: Raise error when dependency could not be resolved via CamelCatalog
URL: https://github.com/apache/camel-k/issues/3449
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3449: Raise error when dependency could not be resolved via CamelCatalog
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3449:
URL: https://github.com/apache/camel-k/issues/3449#issuecomment-1184254005
Relates #3127
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3449: Raise error when dependency could not be resolved via CamelCatalog
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3449:
URL: https://github.com/apache/camel-k/issues/3449#issuecomment-1226866591
I am not sure we do allow any extension, as everything should be present in Camel Quarkus as well. @astefanutti do you recall if we had any extension mechanism in place?
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] claudio4j commented on issue #3449: Raise error when dependency could not be resolved via CamelCatalog
Posted by GitBox <gi...@apache.org>.
claudio4j commented on issue #3449:
URL: https://github.com/apache/camel-k/issues/3449#issuecomment-1241277671
It seems to me there should be a parameter of `kamel run --verify-deps=<true|false>` to allow the integration to run and provide feedback to the user in the case the integrations uses a dependency not in the catalog but is a resolvable one.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3449: Raise error when dependency could not be resolved via CamelCatalog
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3449:
URL: https://github.com/apache/camel-k/issues/3449#issuecomment-1221988293
Can we assume that every available component is really provided in the Camel catalog? For instance, `camel-quarkus-management` is not listed in the Camel catalog 1.13.0. I'm concerned that if we throw errors and reject building it if a dependency is not listed in the catalog we might end up rejecting some projects that are in fact valid in terms of dependencies.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3449: Raise error when dependency could not be resolved via CamelCatalog
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3449:
URL: https://github.com/apache/camel-k/issues/3449#issuecomment-1222030720
I think it should not be related to dependencies but as mentioned in #3127 to capabilities/components.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3449: Raise error when dependency could not be resolved via CamelCatalog
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3449:
URL: https://github.com/apache/camel-k/issues/3449#issuecomment-1226854358
@christophd @squakez BTW, I noticed that if we implement this strict guard on components using catalog, users won't be able to use custom components or renaming of existing components unless we provide a way for the users to extend the catalog. Do we support such use cases right now?
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org