BJ Hargrave

We would have access to the various new language and library features of Java 11. Nothing earth shattering (Java 17 has more interesting new language features). There is nothing requiring...

> I once accidentally build bnd with a JDK 11 and even with java.target 1.8 we became incompatible. Not sure who the culprit was, but in one of our basic...

> Well, why not wait? Ok, but when is the wait over? When will it be time to move to Java 11? Or Java 17?

> Well, I answered that question: when there is a language feature that we could really leverage. That is a very open-ended answer. There are many library features we can...

> Am I missing something? I do not think this will ever happen? Eclipse IDE already requires Java 11 since [2020-09](https://wiki.eclipse.org/Eclipse/Installation#Eclipse_4.17_.282020-09.29). Look in your `eclipse.ini` file: ```properties -Dosgi.requiredJavaVersion=11 ```

> Yes, but that is not for the bundles running on it? Well if Eclipse IDE requires Java 11, then the runtime is Java 11+. Eclipse now ships with [Java...

> I am a bit surprised you mix them up :-) I don't mix them up, at all. > Eclipse will run Java 8 bundles long after I am dead....

> I guess we should just set a date, I would prefer December 2022 this year, and make the move to 17. I'd expect little extra value in going to...

> Shall I make the announcement? Sounds good.

Announcement: https://bnd.discourse.group/t/long-term-plan-to-move-to-java-17/206