Since you are on the topic, do you know if any of these have trouble if you go to a shell and do a `mvn clean` on the project?
I have a plugin (dont remember its name) that integrates Maven nicely, but is allergic to the (sometimes needed) cleaning. Thanks, Rodrigo On Sun, Feb 24, 2008 at 2:09 AM, Jason Chaffee <[EMAIL PROTECTED]> wrote: > I found the following FAQ about Q4E: > http://code.google.com/p/q4e/wiki/FAQ > > > > > Features > > > * running Maven goals from the IDE > * dependency managing using the Maven POM, with automatic download > of dependencies > * keeping Eclipse classpath synchronized with Maven POM > * dependency graphing > <http://code.google.com/p/q4e/wiki/DependencyGraphViewer> > * direct import of Maven 2 projects > * wizard for creation of new projects using the archetype > mechanism > * modular approach to improve reusability by other Eclipse > projects > * ability to import parent projects (pom projects) > <http://code.google.com/p/q4e/wiki/ImportingMultiprojects> (from 0.5.0) > > * ability to cancel maven builds (from 0.5.0) > * dependency analysis tooling (from 0.5.0) > > > > > What are the differences between this plugin and m2eclipse (aka Tycho)? > > > The objective of this plugin is to be part of the Eclipse Foundation > <http://www.eclipse.org> , for that reason the license is EPL and we are > going to follow the foundation procedures. Thanks to the sponsorship of > DevZuz <http://www.devzuz.com> , an Eclipse Strategic Developer Member > <http://www.eclipse.org/membership/showMember.php?member_id=824> we are > in a good position to achieve this goal. > > Besides the objective, there are technical differences. While m2eclipse > shows Maven output in a console, Q is based in events and will show them > in an organized way that allows filtering by severity, search,... > Functionality like the dependency graph, or creation of new projects > using the archetype mechanism are only present in Q. > > Also it's implemented in several modules with reusability and extension > in mind so other people can develop their own plugins taking advantage > of the functionality they need (see for instance Candy for Appfuse > <http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be > -under-extreme-refactoring/<http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be-under-extreme-refactoring/>> > ). > > In any case the underlying Maven libraries used for both plugins are the > same (the Maven Embedder) and both plugin developers collaborate in its > development. > > > > > > > > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris > Sent: Saturday, February 23, 2008 5:45 PM > To: users@maven.apache.org > Subject: Mevenide vs. M2Eclipse, Q for Eclipse/IAM > > > > I googled around to try to find a comparison between Mevenide and the > > alternatives, and didn't come up with much. > > > > Can someone tell me the differences? > > > > (I've spend some time with m2eclipse, and I'm *not* impressed). > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > >
