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

chore: Improve extract Camel catalog script #3221

Merged
merged 1 commit into from
May 13, 2022

Conversation

christophd
Copy link
Contributor

Avoid breaking Makefile when Camel catalog staging repository (e.g. https://repository.apache.org/content/repositories/orgapachecamel-1425) is not available for some reason. In case catalog is empty just log a WARNING and continue with the build.

Release Note

NONE

Avoid breaking Makefile when Camel catalog staging repository is not available for some reason. In case catalog is empty just log a WARNING and continue with the build.
Copy link
Contributor

@squakez squakez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that is a transient situation happening when the staging repo does not exist any longer (it had to be moved because of #3222). IMO we should instead verify that the repo does not exist any longer and fail fast, claiming to the user that the staging repo does not exist.

Copy link
Contributor

@phantomjinx phantomjinx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@christophd
Copy link
Contributor Author

@squakez yes this is transient. as the staging repository is hardcoded in the Makefile the user will not be able to build though until the staging repository is fixed and Makefile is updated. The staged catalog is part of the Camel K repository as a checked in file so I thought ignoring and logging a WARNING is enough

@squakez squakez merged commit 228811a into apache:main May 13, 2022
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 this pull request may close these issues.

None yet

4 participants