kubernetes-client
Umbrella Issue: Java8 incompatible dependencies
The following dependencies failed to be upgraded due to Java8 incompatibility:
- https://github.com/kubernetes-client/java/pull/2773
- https://github.com/kubernetes-client/java/pull/2771
@yue9944882 Perhaps we should move forward to Java11 at one of the major versions?
Alternately we could have a minor version for Java8 and a minor version for Java11 (e.g. 19.1.x == java8, 19.0.x == java11)
Alternately we could have a minor version for Java8 and a minor version for Java11 (e.g. 19.1.x == java8, 19.0.x == java11)
@brendandburns i'm not sure bumping major is easy to users to understand. maybe just adding a .java8 suffix will be more intuitive? 🤔
regarding the spring 17 support, i think we can skip compiling for those java8 incompatible modules in our test job if we want to bump those dependencies to java11, so java8 users can still use the java8-compatible modules anyway. See this commit in https://github.com/kubernetes-client/java/pull/2773: https://github.com/kubernetes-client/java/pull/2773/commits/14f8bc6c1659c7c509e3afc5808631b3763be193, this will only require java17 for those who wants to opt-in to spring support.
as for mockito, i don't see the necessity to bump that at this point? since that it's just a test-dependency. probably we can figure out how to support java8 in long-term when there's a more convincing dependency needs us to upgrade in the future?
Ok, sounds good to me. I figured out how to handle the logback dependency that seemed to have a similar problem, so that's another one off the list.
We can defer this until we're really stuck.
Another Java11+ dependency:
https://github.com/kubernetes-client/java/pull/2782
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
