Hi Norbert,
On 11/08/16 22:37, Norbert Wnuk wrote:
Hi Karl,
In our case this is mostly a matter of the paradigm where (hundreds of)
projects are simple to setup & contribute, part of it is to have entire
configuration in the repository - close to the source code. From maven
perspective to have project specific settings.xml to adjust mirrors (yes -
there are projects with their own repository manager), servers and
sometimes proxies (things that cannot be defined in a pom.xml). Project
specific settings.xml (-s) allows also to avoid problems with users
specific overrides,
Can you give some examples of those user specific overrides?
All the other information I have read....
The point is settings.xml is system specific whereas .mvn/extension.xml,
.mvn/maven.config and .mvn/jvm.config is simply project specific.
Allowing the settings.xml into .mvn/ will violate the design goal here
which is good from my experience...really a separation of concerns..
Apart from that this would make it happen that people might checkin
passwords etc. along with their settings.xml which is very bad...at the
moment this is prevented by design...this can also lead into problems if
you would like to build older project states which would contain such
configuration might fail cause the outer environment has changed in the
meantime cause you have configured some proxies/mirrors/whatever in your
settings.xml which do not exist anymore or have changed...
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
