[
https://issues.apache.org/jira/browse/MSHARED-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754154#comment-16754154
]
Hervé Boutemy edited comment on MSHARED-796 at 1/28/19 6:32 PM:
----------------------------------------------------------------
Yes, recompiling with Java 11, you’ll get different bytecode than the build
done with JDK 8: just try diffoscope and you’ll easily see
on value, it’s the same for everybody, then no need to store it (and create
confusion on spec vs distribution)
was (Author: hboutemy):
Yes, recompiling with Java 11, you’ll get different bytecode than the build
done with JDK 8: just years try diffoscope and you’ll easily see
on value, it’s the same for everybody, then no need to store it
> 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.4.0
>
>
> 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)