-
Notifications
You must be signed in to change notification settings - Fork 22
Conversation
|
@skabashnyuk For kubernetes-client & openshift-client the CQ is opened and reviewer wrote "Please proceed with checkin". For "kubernetes-model" there is no CQ opened and we do not use this library directly (kubernetes-client just depends on it). However, without specifying it in the pom.xm explicitly the build fails with:
Should we open a CQ for it even though it is not used directly ? |
if it's not needed just exclude it like this https://github.com/eclipse/che-dependencies/blob/master/pom.xml#L195-L204 |
@skabashnyuk Do we really need to open CQ for each transitive dependency? I have done some CQs in the past and there were no requests for transitive dependencies processing. For this change we have only one CQ - https://dev.eclipse.org/ipzilla/show_bug.cgi?id=12209 |
yes- if you adding new library and this library added new transitive dependencies.
|
@skabashnyuk could you please take a look at -https://wiki.eclipse.org/Development_Resources/Contribution_Questionnaire#Third_Party_Libraries As far as I am concerned, we do not need to open any CQs for transitive dependencies as long as they are not used directly. So, the only CQ that should be opened is for kubernetes-model - https://dev.eclipse.org/ipzilla/show_bug.cgi?id=12440 |
Can you exclude all transitive dependencies that has not Che CQ? |
@skabashnyuk probably we can exclude some of the dependencies
I have excluded the following dependencies and was able to build "openshift-connector" branch and run the test:
Need to do more testing in order to figure whether those libs are required in the runtime |
I've created the following CQs:
Maven artifacts |
@l0rd ok let us know please when they will be approved |
@l0rd we need to open yet another CQ (got a bunch of NoClassDefFound error while testing):
|
@l0rd it looks like the only dependency that can be excluded is com.github.mifmif:generex:jar:1.0.1 and it's transient dk.brics.automaton:automaton:jar:1.11-8. At least I had no issues during testing. PR was updated with those lib exclusion. For all other dependencies except io.fabric8:zjsonpatch:jar:0.2.3 CQs have already been opened |
I've opened a new CQ for zjsonpatch: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=12451 Here is the list of current CQs. I will check a CQ as soon as with have an approval: |
PR has been updated due to zjsonpatch 0.2.3 copyright header issue:
CQs for "kubernetes-client", "kubernetes-model" & "zjsonpatch" has been updated |
are you going to exclude
? |
@skabashnyuk yup, it is excluded |
Any news? |
@skabashnyuk No news :-( Waiting for zjsonpatch & kubernetes-model CQ clarifications from eclipse IP team |
@skabashnyuk @l0rd Good news! CQ for zjsonpatch has been approved and we got an allowance to proceed with kubernetes-model-1.0.65 checkin. So, I guess the PR can be safely merged now:
|
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.
Need to wait tomorrow before merging. (release will occur today)
Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
PR has been rebased |
We good to go. |
The change is coupled with PR - eclipse-che/che#3381
While building "plugin-docker" without "skip-enforce" profile I got the following error:
In order to make it work I had to add those dependencies to pom.xml even though only "openshift-client" is required. Both kubernetes-client & openshift-client are located in the same repository and the CQ allows to proceed with checkin. However, kubernetes-model is located in different one and no CQ has been created for it. Do we need to create one even though it is not used directly ?
mvn dependency:tree
CQ - https://dev.eclipse.org/ipzilla/show_bug.cgi?id=12209
Jira - https://issues.jboss.org/browse/CHE-55