provisioning Maven settings and other configurationhttps://www.eclipse.org/forums/index.php/mv/msg/1206/3246/#msg_3246
> On a related note. I've been wondering about the best way to manage
> settings.xml for our deployment. I'd like to limit the amount of
> twiddling a developer needs to do while at the same time making the
> m2eclipse configuration "change friendly." In other words, I'd like a
> way to provide settings as well as make them easy to update.
>
> Would an extensions point help? It would be cool if we could have an
> internal eclipse update site that would provide archetype and settings
> extensions. We'd still have to get our folks to manually check for
> updates, but this would be better than pointing folks at docs that
> they may not read.
>
Please list this in the "ideas page" on the wiki [1] and add child
page with more details (similar to Archetype filtering). You may as well
add jira issue for that and link it from the wiki. So, everyone
interested can also comment on that.

We already have need to refactor Maven configuration UI and may as
well consider your requirements for that refactoring. Currently there
are "global" and "user" settings can be specified in "Window /
Preferences... / Maven", but it is somewhat out of sync with "Maven /
Installations" settings, where you can select between Embedded and
External Maven instances. So, the idea is to move "global and user"
settings into installations page and disable "global" settings when
Embedded instance is used. To incorporate your idea, we could expose
extension point that would allow you to bundle your own "Embedded" Maven
instance and/or settings.xml for your infrastructure.

One last thing would be to preconfigure all those settings in custom
product (e.g. set all defaults and things like that). You should be able
to do that in your own plugin that would basically pre-set all required
settings using m2eclipse API or just directly use Eclipse settings.