-
Notifications
You must be signed in to change notification settings - Fork 352
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
do not include runtime artefacts in operator image by default #486
Conversation
fad349d
to
b9ee88f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just a question: why the resources from runtime have version 1.0.0?
they should not have any version set but that's what the camel-k-maven-plugin does at the moment, I'm working on that |
b9ee88f
to
943d1ca
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds ok @lburgazzoli. Which part do you think needs an improvement? All pieces seems clearly separated now.
script/Makefile
Outdated
BASE_IMAGE := fabric8/s2i-java:3.0-java8 | ||
LOCAL_REPOSITORY := /tmp/artifacts/m2 | ||
IMAGE_NAME := docker.io/apache/camel-k | ||
RELEASE_GIT_BRANCH := upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RELEASE_GIT_REMOTE
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
943d1ca
to
cfde28b
Compare
so let see how may thing we'll break |
This PR removes the dependency between camel-k and camel-k-runtime as well a some re-factoring to the build set-up.
Some work is still needed so I definitively need someone to review and suggest cahnges