[JENKINS-20679] - Inject Minimum-Java-Version into the plugin manifest

[oleg-nenashev]

Downstream of jenkinsci/maven-hpi-plugin#75 . It is a more simple version of #133 which should unblock the feature while java.level=11 is not fully supported. So you still build plugins which are formally Java 8 compliant (source/target), but you can require Java 11 due to whatever reason.

• By default, injects versions like 1.8 or 1.7
• Can be overridden to produce 11 for Java 11. Example: Enable test automation for Java 11 and newer Jenkins Core versions label-verifier-plugin#4 and Prepare an experimental release with Java 11 compatibility workflow-support-plugin#82

Consumer of the pull request: jenkins-infra/update-center2#253

@jenkinsci/java11-support

[oleg-nenashev]

3.29-20181203.151310-8 is the new deployment

[batmat]

LGTM

[jglick]

• By default, injects versions like 1.8 or 1.7
• Can be overridden to produce 11 for Java 11.

This seems extremely confusing to me. Why can we not just say it always injects versions in the now-preferred format: 7, 8, 11, etc.?

[oleg-nenashev]

This seems extremely confusing to me. Why can we not just say it always injects versions in the now-preferred format: 7, 8, 11, etc.?

It follows Java specification formats in https://openjdk.java.net/jeps/223 (new ones for modern Javas and old ones for 8 and older)

[oleg-nenashev]

@jenkinsci/java11-support should be ready to go