James Z.M. Gao created MNG-6392:
Summary: Add Project Settings .mvn/settings.xml
Issue Type: New Feature
Components: Bootstrap & Build, Settings
Affects Versions: 3.5.3
Reporter: James Z.M. Gao
Maven originally have two settings slot, user and global. But the project need
and should have more ability to control how itself built by maven. Just follow
the core-extension way, we can add a new settings slot, project settings at
Then the settings merge order from high priority to low is
* project level
* user level
* global level
This order is widely used in many projects such as git.
In the project settings, we should always ignore some _personal local_ fields,
including localRepository, interactiveMode, offline and usePluginRegistry.
With this feature, many things become easy. When we developing multiply
projects from different organizations/companies/envrionments, the maven
configurations may conflict, and are annoying to manage (edit manually or use
some switch scripts each time we switch the project or environment). Another
problem is when using some corp maven repositories or mirros for bootstraping
the team common root poms or core-extensions, the developers have to do some
setup actions. But the projects should be `mvn verify`-ed out of box.
Here is a [fast implementation via
this feature should woks before loading extensions.
This message was sent by Atlassian JIRA