Mevenide has paths hard-coded when it looks for the various dependices required to run Maven. Inserting a new version of Maven with different dependencies (i.e. the new 1.1-beta1) causes Mevenide to fail.
A more dynamic method of locating dependencies (i.e. listing the %MAVEN_HOME%/lib folder and dynamically adding all JARs from there) would be preferable and allow users to update Maven without having to wait for a new version of Mevenide.