[MSHARED-1466] add default MANIFEST entry for release/target JDK

[jira-importer]

Hervé Boutemy opened MSHARED-1466 and commented

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?

---

Affects: maven-archiver-3.6.3, maven-archiver-4.0.0-beta-1

Issue Links:

• MPIR-263 improve minimum java requirement when m-compiler-p not explicitely configured: use default properties
  ("incorporates")

• MPIR-481 clarify Java Version: build, target or release?

• MJAR-323 add Release/Target-Jdk-Spec entries to MANIFEST.MF
  ("is required by")

2 votes, 3 watchers

[jira-importer]

Hervé Boutemy commented

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

[jira-importer]

Piotr Karwasz commented

Target-Jdk-Spec sounds good to me. I don't think it is worth differentiating between maven.compiler.target and maven.compiler.release, since only one of them will be effective.

[jira-importer]

Hervé Boutemy commented

yes, let's keep it simple: we'll see later if more precision is useful