[
https://issues.apache.org/jira/browse/MNG-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031888#comment-17031888
]
Marco Brandizi commented on MNG-6768:
-------------------------------------
[~rfscholte], my use case is:
- I've my PC-specific settings in .m2
- I've my company-dependent settings in <project-dir>/company-settings.xml.
These add and/or override my PC settings (or company server settings).
- I need to do some test that imply using company settings and changing a few
bits of them via an additional test-settings.xml file, which rely on
company-settings.xml definitions.
Yes, I could do it via command line parameters, but adding test-settings.xml
and importing company-settings.xml from the latter can often be better than
writing an .sh (eg, many parameters, many <server> definitions.
Yes, ti could be done by copying company-settings.xml into test-settings.xml,
but that would create redundancy (and it's not always possible, when
test-settings is in places different than <project>, eg, in the CI system).
> Support inheritable multiple settings
> -------------------------------------
>
> Key: MNG-6768
> URL: https://issues.apache.org/jira/browse/MNG-6768
> Project: Maven
> Issue Type: Improvement
> Components: Settings
> Reporter: Marco Brandizi
> Priority: Minor
> Fix For: waiting-for-feedback
>
>
> As far as I know, the --settings option supports just one settings file.
> Worse, when it is used, user settings in ~/.m2/settings.xml are ignored (not
> tried, but I suspect global settings are too).
> To me, this is rather poor. It would be much better if
> # user and global settings were inherited and possibly overridden by the
> further settings file.
> # multiple --settings <file> could be specified and a merge of settings
> could be composed by maven (eg, <profile> blocks would come from multiple
> files, <properties> would be overridden, considering the order in the command
> line).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
