For me, as a full-fledged Maven newbie, the m2eclipse plugin worked fine . We manage about 15 projects. Maven nested projects will be flat in Eclipse (since they do not support nested projects), but they were all automatically configured correctly, so everything works fine. Until now, I have never had to manually launch the Maven command, since the pre-configured “run” as “launch configurations” were used for me, they did their job quite well.
For me, the quality of m2eclipse can be judged by this simple example: if you run Eclipse on the JRE instead of the JDK, then m2eclipse shows a warning that some of its functions rely on the JDK. However, it still runs on the JRE. The warning dialog contains hyperlinks to the Eclipse documentation about the command line arguments and the "Installed JRE" settings, so you can easily fix the wrong Java virtual machine.
This suggests that I cannot speak for or against IAM, as I have never used it because of my good experience with mainlips.
Bananeweizen Dec 07 '08 at 18:59 2008-12-07 18:59
source share