claudio4j commented on issue #4739: URL: https://github.com/apache/camel-k/issues/4739#issuecomment-1719325001
While working on #4715 I did some quick testing using the version scheme `2.16.x` and it will only match the camelcatalogs already installed in the namespace, for example given the camelcatalogs already added to the namespace: ``` camelcatalog/camel-catalog-1.17.0 camelcatalog/camel-catalog-2.16.1 camelcatalog/camel-catalog-2.16.5 ``` If using `camel.runtime-version=1.17.x` or `camel.runtime-version=2.x`, the semver rule can match the mentioned camelcatalogs. However if the user sets `camel.runtime-version=3.x` the semver check will fail and the next step is the camelcatalog controller code to generate the catalog, which will fail because the version `3.x` doesn't exist. In this case forcing the user to set an existing camelcatalog version `camel.runtime-version=3.0.0` -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
