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

Christian Stein sormuras at gmail.com
Fri Oct 11 19:30:12 UTC 2019


On Fri, Oct 11, 2019 at 3:51 PM Brian Goetz <brian.goetz at oracle.com> wrote:

> [...]
> > The way the class format is versioned is proving
> > disastrous for the community.
>
> Again, you’re acting like this is a new thing.  Given that we’ve been
> doing it this way for nearly 25 years, it can’t be all that disastrous.
>

An extreme thought experiment:
Update the class file version every 6 weeks, days, ... and see what happens
to "all" build tools.
A lot of build tools, ranging from foundation tools like `javac` to Maven
will just continue to work.
This also goes for Gradle using its Kotlin-based DSL, if I'm not mistaken.

"If it hurts, do it more often."

I guess, "all" build tools would soon be agnostic to the class file version
-- or updated their
delivery process to match the 6 ... hours cadence.

Cheers,
Christian


More information about the jdk-dev mailing list