Missing sources stepping through Jigsaw code?

[Andrew Dinn]

On 28/07/16 19:11, Alan Bateman wrote:
> On 28/07/2016 19:04, Jason T. Greene wrote:
>> Wow! That's very unfortunate. If there's no way to correlate a source
>> snapshot to an OpenJDK binary; that's going to be a very strong
>> motivator for using a thirdparty build.
>>
> The `release` file in the top-level directory has the hg tips used in
> the build, this has been the way to link it the sources for several years.

As Alan indicated, this is, of course, merely an artefact the EA Jigsaw
releases being Oracle builds. The build system can be configured to
include the missing sources in src.zip and seems to be so configured by
default. I cannot see Red Hat being happy to follow Oracle's policy of
omitting these sources from their OpenJDK releases. Obscurity has never
been the a part of the Open Source way of doing things.

I do think Oracle's policy -- at least wrt re these EA releases -- is
rather self-defeating. It would actually be of great aid to those of us
currently trying to help validate the proposed solutions to the
outstanding Jigsaw issues if we could see what is going on inside the
Jigsaw code from a debugger. Not everyone involved is in a position to
build (and keep on rebuilding) a Jigsaw JDK9 release from scratch.
Still, no doubt Oracle has its own reasons for adopting such a policy.

regards,


Andrew Dinn
-----------
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander