RFR: 8224974: Implement JEP 352

[Andrew Dinn]

Hi Alan,

On 10/06/2019 09:18, Alan Bateman wrote:
> I don't have any other feedback on the JEP beyond my last mail about
> removing the "Proposed Java API Changes" section from the Description.
> Once we you ready then Brian (as area lead) should be contacted to seek
> his endorsement.
I have updated the Proposed Java API Changes to remove the changes to
map exception signature and force region specification. They were
covered in the prior enabling JIRAs/CSRs.

So, the remaining two sections mention 1) the new module + package +
enum and 2) the bean counting changes. The new section 1 clarifies when
UnsupportedOperationException is thrown vs when IOException is thrown as
part of the explanation of what the new modes are for.

I also added a paragraph to the alternatives section explaining that
Panama was and still is an alternative option and why we decided to
proceed with this model despite it being still under consideration.

Finally, I am unclear whether the presence of the new module + package
means this is an SE JEP or a JDK JEP? In the latest update I have
assumed the JEP type is still JDK and changed the title for the public
API changes to "Proposed Java API Changes". Is that right? Or do you
want the JEP type to be SE and have the title remain "Proposed Java SE
API Changes"

regards,


Andrew Dinn
-----------