@Andreas, no I think Andrei was being too quickly dismissive over the Maven Eclipse plugin, which is still alive and well. The link Andrei gave in (1) gives further cause for concern, as it seems to imply (if I'm understanding it correctly) that m2e is now doing a build process procedure different from what Maven proper would use.
We don't use m2e (or Eclipse for that matter) to build Karaf-
we use IDE-independent Maven-"mvn clean install" is the one authoritative and official way to build the application, regardless of the IDE you use. m2e is primarily a cute graphical tool for Eclipse users who don't like having a command window open for building and using mvn eclipse:eclipse to import their projects into Eclipse. Now, with the latest version m2e apparently wants to do its own build process following its own build algorithm. I'm not sure supporting multiple build processes (m2e and Maven proper) is a good idea.
My initial concern is that m2e is requiring declarations in POM files, as well as discontinuing support of the output generated by mvn eclipse:eclipse, to get a listing in everybody's POMs with the eventual goal of requiring Eclipse and m2e usage whenever you want to build a Mavenized application. But perhaps that is unlikely, and this is just one declaration in a parent-level POM and everything's OK. If so, fine. But be careful that this doesn't get more intrusive over the poms, as we need to make more and more pom.xml changes for m2e builds to work, eventually becoming dependent on m2e as pure-Maven builds no longer work. And when you become dependent on m2e for your builds, then you lose IDE independence as well.