Please stop incrementing the classfile version number when there are no format changes

[Dalibor Topic]

On 11.10.2019 16:15, Cédric Champeau wrote:

> FWIW, Gradle 6 is planned to be released this month, with an RC next week.

Thanks, Cedric, that's great news!

On a side note, some people might think that once a JDK release comes 
out, only then everyone in the broader ecosystem can start to scramble 
to be able to support it. That's not correct.

To put things into perspective about the ability of the ecosystem to 
adapt to new classfile versions:

* ASM 7.1 with support for Java 13 opcodes was released on March 3rd 
[0], more than six months ahead of JDK 13, the then next release in the 
six-monthly JDK release cycle.

(For example, Groovy 2.5.7 with ASM 7.1. was released two months later, 
on May 12th. [1])

* ASM 7.2 with support for Java 14 is available since September 29th, 
again roughly 6 months ahead of planned JDK 14 GA.

* JDK 14 EA builds have been available since this summer. [2]

* The OpenJDK Quality Outreach is there to assist OSS projects 
interested in testing upcoming JDK releases [3] over on 
quality-discuss at openjdk.java.net.

cheers,
dalibor topic

[0] https://asm.ow2.io/versions.html
[1] https://blogs.apache.org/groovy/entry/groovy-2-5-7-released
[2] https://jdk.java.net/14/
[3] https://wiki.openjdk.java.net/display/quality/Quality+Outreach
-- 
<http://www.oracle.com>
Dalibor Topic | Consulting Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961> | Video: dalibor.topic at oracle.com
<sip:dalibor.topic at oracle.com>

Oracle Global Services Germany GmbH
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRB 246209
Geschäftsführer: Ralf Herrmann

<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment