It looks like they are in the same league functionality wise. I didn't know about Mevenide when I made Maven Workshop. Although I haven't tried it, Mevenide looks to be stronger with the context-assist editors. Mevenide seems like a real good plug-in. Maven Workshop has a good project wizard which basically lets you define your own project wizards. Maven Workshop also has more classpath management functionality (again, judging from the Mevenide features page) to add individual dependencies and create dependency groups and stuff like that.
Joe
Guest
Post subject:Posted: Jul 14, 2004 - 12:20 PM
Indeed maven oriented wizards that Mevenide provides still need to be polished to let the user have more control on the generated stuff. however concerning the classpath manipulation mevenide basically provides the same functionnalities than mavenworkshop (altho in a different way - using a view and taking folders into accoutn too) : user can add and remove dependencies from .classapath and/or project.xml. what mevenide lacks is the ability to define dependencies group (something like the eclipse 3 user libraries), but this is *not* something that will be supported by mevenide, indeed this seems to me like a workaround for the lack of the transitive dependencies in maven. so when maven will support it, mevenide will as well.