maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norbert Wnuk <>
Subject Re: MNG-5930 - lack of system properties expansion
Date Thu, 11 Aug 2016 20:37:01 GMT
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, (i.e. from multiple other projects) in their
.m2/settings.xml, for frequent switches between projects. MNG-4686
describes very similar use case except I prefer to have single settings.xml
file in .mvn directory to indicate project specific settings.xml by
The problem with .mvn/maven.config now is that settings.xml location must
be absolute to be able to invoke mvn command from sub-project level -
MNG-5859/MNG-5790. MNG-5930 is not my use case since I need only
expansion to effectively access all files in the repository. Generally
would like to have .mvn/settings.xml location treated the same like
extensions.xml / jvm.config / maven.config however the approach with
maven.config and ${maven.multiModuleProjectDirectory} property / all system
properties expansion seems to be less intrusive and slightly more generic.


On Thu, Aug 11, 2016 at 9:08 PM, Karl Heinz Marbaise <>

> Hi,
> can you explain why you have the need for different
> mirrors to be defined ?
> Are you using a repository manager ?
> Related to MNG-4686[1] I'm thinking what's the reason to have a different
> local caches?
> Kind regards
> Karl Heinz
> [1]:
> On 10/08/16 01:16, Norbert Wnuk wrote:
>> Hi All,
>> I was wondering whether the statement that lack of system properties
>> expansion in maven.config has be done by design and it is rather unlikely
>> to change it is still valid (MNG-5930, commented by Jason). Below a link
>> to
>> the tiny change that would help me with i.e. MNG-4686, even the more
>> narrow
>> filtering as described in MNG-5859 would be sufficient for me (mainly to
>> allow for project specific settings.xml files with i.e. different mirrors
>> that cannot be defined in pom.xml).
>> Wanted to confirm how desirable this change is / which approach would be
>> more likely to be accepted if at all.
>> 4b4b71e428030f37af3102bb
>> Regards,
>> Norbert
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message