[
https://issues.apache.org/jira/browse/MNG-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762193#comment-16762193
]
Michael Osipov commented on MNG-6124:
-------------------------------------
Do we still need this?
> Add <user> section in settings.xml
> ----------------------------------
>
> Key: MNG-6124
> URL: https://issues.apache.org/jira/browse/MNG-6124
> Project: Maven
> Issue Type: New Feature
> Components: Settings
> Affects Versions: 3.3.9
> Reporter: Anthony Vanelverdinghe
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> Maven uses the login name (i.e. the system property user.name). 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|https://issues.apache.org/jira/browse/MSHARED-362]), because:
> - 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 <[email protected]>) like hg.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
