maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Closed] (MNG-6124) Add <user> section in settings.xml
Date Wed, 03 Apr 2019 20:19:00 GMT


Michael Osipov closed MNG-6124.
       Resolution: Incomplete
    Fix Version/s:     (was: waiting-for-feedback)

No feedback received.

> Add <user> section in settings.xml
> ----------------------------------
>                 Key: MNG-6124
>                 URL:
>             Project: Maven
>          Issue Type: New Feature
>          Components: Settings
>    Affects Versions: 3.3.9
>            Reporter: Anthony Vanelverdinghe
>            Priority: Major
> Maven uses the login name (i.e. the system property In particular, it uses
it in the Maven Archiver, to set the "Built-By" manifest entry. However, in my opinion this
is problematic (see also [MSHARED-362|]),
> - login names can typically only be traced back to a person within an organization
> - outside of an organization, login names may be ridiculous, embarrassing, ... and I'd
guess many people are unaware of the fact that their login name is disclosed in any artifact
they build
> Other systems, such as git and hg, actually use the login name as well by default. However,
they allow to set the username in their global configuration. Maven should allow the same,
setting both a username and an e-mail. Either by having 2 properties username and user e-mail,
like git. Or by having a single property username, where the e-mail can be appended (e.g.
Anthony <>) like hg.

This message was sent by Atlassian JIRA

View raw message