Some background on this:
I initially introduced VERSION_SPECIFICATION as VERSION_MAJOR but had to revert
it in the Verona branch since I was told that the specification number should
be identical to the release version. My initial reaction was the same as yours,
that the specification would mat
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
th
On 28/07/2016 17:58, Andrew Dinn wrote:
:
2) More pertinently, is this merely a reflection of Oracle's policy
regarding distribution of sources or is this also the policy adopted for
OpenJDK builds?
Yes, it's a policy issue (outside of our control, and not specific to
Jigsaw EA builds). If y
n.b. I'm addressing this question to the Jigsaw list a sit appears to
relate to the organization of the code base into modules but I have
copied it to build-dev just in case it simply relates to the build config.
While debugging my Jigsaw ModuleFinder implementation I noticed that the
src.zip file
On 28/07/2016 11:15, Seán Coffey wrote:
such packages are not in the scope of the OpenJDK project. I'll ping you
offline with some contacts.
Any reason why that's the case? All the tools needed to build IPS
packages are available as standard on Solaris.
--
Alan Burlison
--
Hi Martin,
such packages are not in the scope of the OpenJDK project. I'll ping you
offline with some contacts.
Regards,
Sean.
On 28/07/2016 10:58, Martin Walsh wrote:
Hi,
I am currently building the JVM on Solaris 11.3. I am trying to
figure out how to build IPS packages from the SVR4 pa
Hi,
I am currently building the JVM on Solaris 11.3. I am trying to figure
out how to build IPS packages from the SVR4 packages in my build
directory. Could anyone provide any insight in how to do this?
Thanks,
Martin
Hi, Volker.
Thanks for your patience.
I think that the solution that you've provided solves the immediate problem,
the java.specification.version number is incorrectly set to be identical to
java.version. The java.{vm.}?specification.version system properties should be
independent of java.ver
