[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jdt-dev] About Y-Builds (was Re: 4.35 Y-Build: Y20250111-1000 - BUILD FAILED)
|
Am 18.01.25 um 21:36 schrieb Mickael Istria:
Please see https://blog.jetbrains.com/idea/2018/10/preview-raw-string-literals-
in-intellij-idea-2018-3/ <https://blog.jetbrains.com/idea/2018/10/preview-raw-
string-literals-in-intellij-idea-2018-3/> for instance. For at least 6 years,
JetBrains has managed to (explicitly) ship support for not yet released Java
features (with some disclaimer) and so far so good for them.
Nice, but JetBrains won't help me if I get into trouble with Oracle. And maybe
JetBrains even has a special contract with Oracle that allows this?
With the above you might, however, be able to get a corresponding statement from
Eclipse Foundation legal staff. That's whom I trust.
Once that were settled we'd be only left with the process problem: if people
start developing parts like DOM / core.manipulation targeting Java X+1 features
in master, while other implementation for the same Java version is being
developed in a beta branch, then the situation will be much crazier than it ever
was in the past. In my view such uncoordinated development would actually feel
close to a project fork. Is that what you want?
Are you really unable to find any open tasks for making IDE support for Java 23
great? Spoiler: perhaps you won't even notice anything new in Java 24 ;-P
thanks,
Stephan