On 6 Aug 2015, at 21:41, Scott Stark wrote:
It came up at the Java EC level that there was not going to be a
public replacement. Hence, there was a concern raised and the OpenJDK
teams have most recently replied with a new JEP that is addressing
this issue.
http://openjdk.java.net/jeps/260 (JEP 260: Encapsulate Most Internal
APIs)
Mark Reinhold wrote this email 2 days ago, that (im my understanding)
says that Unsafe will stay:
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-August/004433.html
This then refers to JEP 260, which says that Unsafe should stay as is.