It really doesn't affect EAP 6. We just documented that it used private APIs and do not plan to change it because the public API isn't available in that release. We just need to fix it for EAP 7.