Fix constructor access check through reflection
We must not throw IllegalAccessException if the constructor has been made accessible by a previous call to Constructor.setAccessible, even if the caller cannot access the constructor. Bug: 20639158 (cherry picked from commit 2d2f2a9c) Change-Id: Ic5cb54256f11aefcfaa99f2ee85c4a32f30e693a
Loading
Please sign in to comment