On 01/12/2014 21:09, Seán Coffey wrote:
On 01/12/2014 18:54, Daniel Fuchs wrote:
on the test side would it be worth testing all public classes available
(e.g in rt.jar ?) to ensure that
Field.setAccessible works as expected and that we don't hit this issue
again ? It might be some
what of a heavy test for jtreg inclusion though.
It could be worth a try. But let's wait until JEP 220 is in.
I'm not sure why JEP 220 would be a factor for now.
I assume this is only because the test would need changes to use the
"jrt" file system to locate all class files (and infer the type names).
-Alan.
