I checked and the issue still exists with 5.0.2.Final. I also updated the test case to the new dependency and uploaded it with a "_5_0_2" prefix.