RFR: 8072379: Implement jdk.Version and jdk.OracleVersion
iris.clark at oracle.com
Wed Jan 13 21:54:44 UTC 2016
Thanks for looking at this (hopefully) one last time.
> It can't be java.base (see design principles in JEP 200).
> If it's going into java.base temporarily then the top-level
> modules.xml will need to be updated to export the "jdk" package.
This diff has been applied to modules.xml:
diff -r 6fefc5bce180 modules.xml
--- a/modules.xml Wed Jan 13 13:56:19 2016 +0000
+++ b/modules.xml Wed Jan 13 13:46:56 2016 -0800
@@ -205,6 +205,9 @@
It essentially reverts your 8049422 change  to that file. I will
not re-add jdk to the javadoc bundle for javac trees API since that
is not an appropriate location. I filed the following bug to track
publication of jdk.Version:
8144069: Determine correct publication for jdk.Version API
When this came up earlier, I filed this bug to track finding
a more appropriate module for jdk.Version:
8144062: Determine appropriate module for jdk.Version
From: Alan Bateman
Sent: Tuesday, January 12, 2016 7:41 AM
To: Iris Clark; core-libs-dev at openjdk.java.net; verona-dev at openjdk.java.net
Subject: Re: RFR: 8072379: Implement jdk.Version and jdk.OracleVersion
On 11/01/2016 21:44, Iris Clark wrote:
> Hi, Joe, Roger, Alan, Magnus, and Mandy.
> At the end of December (shortly before the Christmas/Winter break and
> my vacation), I provided responses to your messages and an updated
> I didn't hear from anybody, so I'd like to optimistically assume that
> you were satisfied. Is that correct?
> For you convenience, here's a reference to the December and November
> I'd like to wrap up this work for the initial implementation of
> jdk.Version soon.
I think this looks good but we'll to decide which module to put this in.
It can't be java.base (see design principles in JEP 200). If it's going into java.base temporarily then the top-level modules.xml will need to be updated to export the "jdk" package.
More information about the verona-dev