This is the cleanup for a complex 2-phase commit changing a package name from java.dyn to java.lang.invoke, in the JDK, JVM, and langtools.
Here's the approximate timeline:
b130: 7017414 in langtools: Release javac which supports both java.dyn and java.lang.invoke.
b135: 6839872/7012648 in JVM: Release JVM which supports both java.dyn and java.lang.invoke.
b136: 6839872/7012648 in JDK: Release JDK which uses only java.lang.invoke.
b137 (or later): 6981791 (this bug) in JVM and 7028405 in langtools: Release cleaned-up JVM and javac, purging all java.dyn references.
We can't remove transitional code (for java.dyn) in the JVM until the meth-rename-7012648 change (java.lang.invoke) in the JDK works out (into b136 or b137).
If we yank JVM support for java.dyn while the b135 JDK code is alive, we'll get lots more failures.
This assumes that the bulk of testing (in various phases) is using the released build. If this is so, we can only cut support from the JVM and javac after the new JDK has released. And of course, we could not release the new JDK until the transitional JVM and javac were released (b135 and b130).