[
https://issues.apache.org/jira/browse/MSHARED-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929454#comment-17929454
]
Herve Boutemy commented on MSHARED-1466:
----------------------------------------
MPIR-263 prepared in-depth algorithm for that
https://github.com/apache/maven-project-info-reports-plugin/blame/master/src/main/java/org/apache/maven/report/projectinfo/SummaryReport.java#L145
> add default MANIFEST entry for release/target JDK
> -------------------------------------------------
>
> Key: MSHARED-1466
> URL: https://issues.apache.org/jira/browse/MSHARED-1466
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
> Affects Versions: maven-archiver-3.6.3, maven-archiver-4.0.0-beta-1
> Reporter: Herve Boutemy
> Priority: Major
>
> we currently have {{Build-Jdk-Spec}} by default
> https://maven.apache.org/shared-archives/maven-archiver-3.6.3/#manifest
> it documents the JDK major version used during the build: ok, why not
> but what users really need is the target bytecode version = the minimum JRE
> version that they'll have to use
> = what we put in documentation as "Java Version"
> https://maven.apache.org/shared-archives/maven-archiver-3.6.3/summary.html
> recording it in MANIFEST.MF would make it much more accessible:
> {{Target-Jdk-Spec}} and {{Release-Jdk-Spec}} based on
> {{maven.compiler.target}} or {{maven.compiler.release}} properties?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
