This is a known problem with 2.0 final, it has been discussed here in the Bug Reports area.