I think it would be reasonable to expect that the fix for that issue which appeared to be present in 1.5-SNAPSHOT will have made it out with release version 1.5. But, you can't assume anything so I would strongly recommend that you
test out for yourself, with the most recent version, the particular usage scenario that you are intending to employ it for.