Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review usage of version constraints #1126

Closed
nicolaferraro opened this issue Dec 6, 2019 · 1 comment · Fixed by #1141
Closed

Review usage of version constraints #1126

nicolaferraro opened this issue Dec 6, 2019 · 1 comment · Fixed by #1141
Assignees
Milestone

Comments

@nicolaferraro
Copy link
Member

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..

@nicolaferraro nicolaferraro added this to the 1.0.0-CR1 milestone Dec 6, 2019
@lburgazzoli
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants