Exether commented on issue #4395: URL: https://github.com/apache/camel-k/issues/4395#issuecomment-2133994280
We definitely thought about this option (renaming kamelets in case of non compatible change), but it quickly seemed unpractical for the following reasons: Kamelet management: - It can be difficult to evaluate if a change needs to create a new version. - In case of a jar changes, several kamelets could require a name change. - This leads to a lot of duplication as we also need to keep the previous kamelets. - It will be difficult to tell if an old kamelet can be removed to keep the overall number low. Routes and config management: - It requires all routes using this kamelet to be updated to use the new one. - It requires to change all the property names for this kamelet in all deployments. - There would be a risk to have several versions of the same library if we freeze older kamelets versions 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-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
