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
We use by default camel-version ">= x.x.x" and runtime.version ">= y.y.y". But not having a precise version caused problems when e.g. a catalog for some reason is not present and it should be created.
I wonder why we don't default to a specific version and use constraints only when the user opt for them..
The text was updated successfully, but these errors were encountered:
I remember we introduced constraints when runtime and camel were moving much faster and we added them for convenience but I do agree that now we should to stick to fixed versions
We use by default camel-version ">= x.x.x" and runtime.version ">= y.y.y". But not having a precise version caused problems when e.g. a catalog for some reason is not present and it should be created.
I wonder why we don't default to a specific version and use constraints only when the user opt for them..
The text was updated successfully, but these errors were encountered: