Am 2021-08-10 um 08:21 schrieb Benjamin Marwell:
I read Michaels message the way like option 6:

Since we have only two files: installation and user, I'd expect
that first the installation settings are parsed followed by user
settings (generic to specific).

Installation is more generic (global) than user.

Same for git: it will first parse the installation settings (/etc), then
any user settings, then any project settings.

/etc isn't installation settings. It's system settings.

Or are we mixing up terms here?

No, Robert created option 7 which reflects your and my view.

On Mon, 9 Aug 2021, 16:35 Robert Scholte, <[email protected]> wrote:

I'll add it, but it doesn't match the order of GIT[1] as mentioned by
Michael.
Maybe there should be a list of other comparable tools with their order


Robert


[1] https://git-scm.com/docs/git-config#FILES
On 9-8-2021 15:09:30, Benjamin Marwell <[email protected]> wrote:
Hi Robert,

I would like to propose another solution.
According to the wiki page and to the documentation, we have

user

where "

 From what I understand from other build systems, a more common approach
would be

installation (aka global)

This would fix the naming issue (global becomes global).
Of course this is a breaking change, but for maven 4, this seems
reasonable to me.

Am So., 8. Aug. 2021 um 11:48 Uhr schrieb Robert Scholte :

During a discussion with Michael we noticed there's something odd about
the names of some flags and the order of inheritance.

I've tried to explain it on a separate wiki page[1] together with the
first 3 options how we could fix it.
Please have a look at it and share your thoughts.

thanks,
Robert

[1]
https://cwiki.apache.org/confluence/display/MAVEN/Commandline+inheritance

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to