-
Notifications
You must be signed in to change notification settings - Fork 863
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
Drop Java 7 support for both the API and SDK #1649
Comments
@AloisReitbauer @Oberon00 @thisthat If we /you can create a fork for dynatrace ASAP, we could get this done before GA. |
Duplicate of #1543 |
Disagree. That issue is about making a decision. This issue is about executing that decision. Dynatrace is the only vendor who has interest in Java 7 support at this point, and out-of-band discussion has indicated that you/they would be amenable to maintaining a Java 7 fork of the project. |
Since Dynatrace is the only vendor that requires Java 7 support in OpenTelemetry, it sounds like creating a Java 7 fork (e.g. https://github.com/open-telemetry/opentelemetry-java7) with Dynatrace folks as maintainers would be a good way forward from this impasse. Btw, other vendors are planning to support the small number of customers that are still on Java 7 by using the prior generation of their java agent/tracer, not sure if this is an option for Dynatrace as well? |
This was a misunderstanding and Dynatrace will not fork, maintain, and support OTel for Java 7 openly. |
Honestly, it was to force the decision to happen, and make sure that it didn't get stalled, which it was looking like it was. |
Why open a new issue though, instead of commenting on the old one? |
So, does this mean Dynatrace is ok with us moving to java 8, or not? |
I commented on #1543. |
hi want to take it this up how to proceed any suggestions. |
@AkshayBabbar Yes, this is now done. Closing! |
Let's make the minimum JDK requirement java 8.
The text was updated successfully, but these errors were encountered: