Thanks to Maven: The Definitive Guide, I was able to answer some questions I had about m2eclipse as well as learn more of it.
When you put a plugin in the build part of the pom, how comes some are running on each source modification and others not ?
The reason is simple : m2eclipse runs by default the plugins in the process-resources phase. Furthermore, this is set up in the Preferences/Maven part of eclipse (but the settings affects all projects, which was a bit overkill for us)?
One can ask m2eclipse to display the projects’ maven version, through Preferences/General/Appearance/Label Decorations and then check “Maven Version Decorator”. Comes handy when having to update different versions of different plugins.
Last but not least, the pom editor “Dependency hierarchy” tab is in fact pretty useful :$
Before I was looking at the “Maven Dependencies” folder to figure out what was there, but in fact this tab displays it nicely.
Two lists are shown there : “Dependency Hierarchy” and “Resolved dependencies”. The first one allows to figure out what was rejected (and from where in the dependencies), the second one shows what is in.
A search is available and run on both lists. So if you wonder about spring dependencies issues, just put spring in the search field, and you all artifact ids containing spring are highlighted.
Hope it helps !