RFR(s): 8204243: remove Thread.destroy() and Thread.stop(Throwable)

[Stuart Marks]

On 6/1/18 5:15 PM, David Holmes wrote:
> I would expect the CSR that marked them as deprecated for removal, also serves 
> for the actual removal. Certainly for VM flags we don't do a separate CSR for 
> each phase (deprecation, obsoletion, expiration).

Hm. Well, this hasn't been tested for Java SE APIs yet, as most of the 
deprecations-for-removal occurred in Java SE 9, before the CSR was active. 
Instead, those deprecations went through the (Oracle internal) CCC process.

Now that we're fully on the CSR system, I'd expect that deprecations (whether or 
not for removal) and removals of Java SE APIs would have separate CSR requests. 
The reason is that adding or changing a deprecation annotation is a spec change, 
and removing the API is a distinct spec change. They also occur in different 
releases.

I can easily see that a different procedure would be followed for VM flags, 
though, since they aren't part of Java SE.

s'marks