Hi!
I gave this few thoughts over Christmas, and my opinion remains. It is better to have
default distro bytecode version then to stick on upstream for 100%. If the change of
projects source/target would kill the project, then it is always easy to turn back to it.
As it seems, Fabio is already more fat then me, then I condemn myself to helping hand
only.
It may be that I'm just to scared of boring source/target amending when jdk17
arrives.
J.
On 12/7/20 11:23 AM, Jiri Vanek wrote:
Hi!
I had risen this topic during jdk11 bump. but it somehow get lost.
The idea is, to provide rpm macros, keeping the default source/target eventually - for
jdk11 and up -the release - numbers for javac to use.
Then to provide tooling, which will help packagers to use them - for ant and maven it
should be simple. For others, probably nothing to do on our side, each packager will be
able to patch/sed theirs builds as necessary (Still it will help a lot for future).
I do not know how to provide them as default (except hardcoding in xmvn, and only allow
to disable them on demand).
This will smooth the bump to jdk17 in f36 really a lot.
Thoughts?
J.
--
Jiri Vanek
Principal software QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com M: +420775390109