We will document a workaround for 5.1.1. That's why I close this bug as "Won't Fix" for 5.1.1. Also the bug isn't affect 6.0 release, so closing it as "Invalid" for 6.0.
We will document a workaround for 5.1.1. That's why I close this bug as "Won't Fix" for 5.1.1. Also the bug isn't affect 6.0 release, so closing it as "Invalid" for 6.0.