maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MSHARED-787) Add optional buildEnvironment information to the manifest
Date Mon, 21 Jan 2019 16:43:00 GMT

    [ https://issues.apache.org/jira/browse/MSHARED-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748081#comment-16748081
] 

Hervé Boutemy commented on MSHARED-787:
---------------------------------------

what is important to me is that by default we have only java.specification.version
but if people configure it, they can get very detailed info like java.version, os details
and so on in Manifest if they want: in Manifest, this will be "the non-reproducible way",
while with buildinfo, it will be "the reproducible way": it's good to have both options available
and people choose their preferred option

> Add optional buildEnvironment information to the manifest
> ---------------------------------------------------------
>
>                 Key: MSHARED-787
>                 URL: https://issues.apache.org/jira/browse/MSHARED-787
>             Project: Maven Shared Components
>          Issue Type: New Feature
>          Components: maven-archiver
>    Affects Versions: maven-archiver-3.3.0
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: maven-archiver-3.3.1
>
>
> People are demanding to have more control about the build information (MSHARED-362).
We should add the following to control this: {{<addBuildEnvironmentEntries}} /> which
is by default disabled. It will contain the folling properties (akin to {{mvn- v}}):
> {noformat}
> Created-By: Apache Maven ${maven.version}
> Build-Jdk: ${java.version} (${java.vm.vendor})
> Build-Os:  ${os.name} (${os.version}; (${os.arch}){noformat}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message