I just had this problem using v2.5.0 of the plugin. I believe the cause is actually a JDK bug, see https://bugs.openjdk.org/browse/JDK-8285966 which was resolved by the DUP https://bugs.openjdk.org/browse/JDK-8285445.

I updated to a JDK version with this issue fixed and the plugin file path problem did not happen anymore.