You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a capability is definitively easy but harmonizing the properties could be a very hard and fragile work as quarkus may introduce new properties and we also need to distinguish between build and runtime ones.
I think one day we may default to quarkus as runtime ....
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k-runtime
that referenced
this issue
Jun 4, 2020
It's currently possible to configure opentracing via quarkus using instructions from https://camel.apache.org/camel-quarkus/latest/extensions/opentracing.html#_usage.
Running the integration with command:
But it uses quarkus properties and the same feature is not available in plain main.
I wonder if this is a case for adding a capability.
I don't know also if we can uniform those properties between environments.
The text was updated successfully, but these errors were encountered: