[
https://issues.apache.org/jira/browse/MSHARED-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748160#comment-16748160
]
Michael Osipov edited comment on MSHARED-787 at 1/21/19 7:05 PM:
-----------------------------------------------------------------
By
bq. while with buildinfo, it will be "the reproducible way"
you mean that this information will be held out of band (outside of the JAR)?
My problem isn't having {{java.specification.version}} by default, but what
benefit gives it to the user when you don't have the {{Build-Maven-Version}}
also. MSHARED-362 would still remain open :-(
was (Author: michael-o):
By
bq. while with buildinfo, it will be "the reproducible way"
you mean that this information will be held out of band (outside of the JAR)?
My problem isn't having {{java.specification.version}} by default, but what
benefit gives it to the user when you don't have the {{Build-Maven-Version}}
also.
> 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)
