On 29/07/2016 10:43, Andrew Dinn wrote:
:
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.
I thought there was an FAQ on this but I can't find it. It comes up
periodically but basically Oracle builds do have some code and modules
that are not in OpenJDK, the deploy area (Java Web Start for example)
mostly. Oracle builds have include the FX modules. They are in the
OpenJFX project (in OpenJDK), just not in the JDK 9 forests so you
typically don't have them in your own builds (needs a configure option
when building).
In any case, src.zip is just the .java sources. The IDEs/debuggers have
historically used it. I don't know if it's used elsewhere but it has
never been the complete source code. It has never include the hotspot
code or any of the native code for example.
The only thing about src.zip that is interesting to modules is whether
to change the layout so that the contents are organized by module. We
have been shy about changing it, mostly because it's not clear what
might be depending on it.
-Alan
