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

Drop Java 7 support for both the API and SDK #1649

Closed
jkwatson opened this issue Sep 15, 2020 · 13 comments
Closed

Drop Java 7 support for both the API and SDK #1649

jkwatson opened this issue Sep 15, 2020 · 13 comments
Labels
release:required-for-ga Required for 1.0 GA release

Comments

@jkwatson
Copy link
Contributor

jkwatson commented Sep 15, 2020

Let's make the minimum JDK requirement java 8.

@jkwatson
Copy link
Contributor Author

@AloisReitbauer @Oberon00 @thisthat If we /you can create a fork for dynatrace ASAP, we could get this done before GA.

@Oberon00
Copy link
Member

Duplicate of #1543

@jkwatson
Copy link
Contributor Author

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.

@trask
Copy link
Member

trask commented Sep 17, 2020

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?

@danielkhan
Copy link

This was a misunderstanding and Dynatrace will not fork, maintain, and support OTel for Java 7 openly.

@Oberon00
Copy link
Member

Oberon00 commented Sep 17, 2020

@jkwatson

Duplicate of #1543

Disagree. That issue is about making a decision.

You have a point, but then why is the issue for making the decision still open while we already have an issue for executing a decision? 😉

@jkwatson
Copy link
Contributor Author

@jkwatson

Duplicate of #1543

Disagree. That issue is about making a decision.

You have a point, but then why is the issue for making the decision still open while we already have an issue for executing a decision? 😉

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.

@Oberon00
Copy link
Member

Why open a new issue though, instead of commenting on the old one?

@jkwatson
Copy link
Contributor Author

This was a misunderstanding and Dynatrace will not fork, maintain, and support OTel for Java 7 openly.

So, does this mean Dynatrace is ok with us moving to java 8, or not?

@Oberon00
Copy link
Member

I commented on #1543.

@AkshayBabbar
Copy link

hi want to take it this up how to proceed any suggestions.

@Oberon00
Copy link
Member

Oberon00 commented Sep 21, 2020

Hi, PR #1665 "Switch to java 8" was already merged, so I don't think there is any immediate action. I hope that a "Java 8 feature using cleanup" or something like that is done after #1631.

But @jkwatson is the one that should really answer this 😃

@jkwatson
Copy link
Contributor Author

@AkshayBabbar Yes, this is now done. Closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:required-for-ga Required for 1.0 GA release
Projects
None yet
Development

No branches or pull requests

5 participants