Which version of maven 2 were you using? We actually did not test 3.3.1 with Maven 3, I believe you were having another kind of maven resolution issue (perhaps a temporary glitch with the repo or things like that). If you want to share some details on the additional investigation, feel free to do so.