maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MSHARED-796) use java.specification.version instead of java.version in Build-Jdk manifest entry
Date Tue, 22 Jan 2019 22:59:00 GMT

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

Hudson commented on MSHARED-796:
--------------------------------

Build succeeded in Jenkins: Maven TLP » maven-archiver » master #49

See https://builds.apache.org/job/maven-box/job/maven-archiver/job/master/49/

> use java.specification.version instead of java.version in Build-Jdk manifest entry
> ----------------------------------------------------------------------------------
>
>                 Key: MSHARED-796
>                 URL: https://issues.apache.org/jira/browse/MSHARED-796
>             Project: Maven Shared Components
>          Issue Type: Wish
>          Components: maven-archiver
>    Affects Versions: maven-archiver-3.3.0
>            Reporter: Hervé Boutemy
>            Assignee: Hervé Boutemy
>            Priority: Major
>             Fix For: maven-archiver-3.3.1
>
>
> as part or reproducible builds efforts, we're removing manifest entries that are hard
to reproduce and do not add much value.
> In MSHARED-661, we removed "Built-By: <username>" entry, but decided to keep "Build-Jdk"
entry
> the idea here is not to remove "Build-Jdk" entry but to replace its value from too much
detailed java.version system property (which details the patch level) to java.specification.version:
the specification has an impact on the generated bytecode, then is useful to keep, but at
least we'll avoid patch level information



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

Mime
View raw message