It is not clear what bytecode level feature is being utilised to require JRE11 at runtime, or if this was just the release engineering JDK used on the day of the release (no technical reason).
Previous releases 4.0.0 used Java8 bytecode, 4.1.0 appears to be using Java11 bytecode with Java8 features (i.e. no new Java 11 APIs are utilized). As a published plugin it is good to consider this area. You ideally want the support the oldest JDK at runtime that matches the oldest Gradle version it is compatible with, so if Gradle works then this plugin just works.
So if 4.1.0 is compatible with Gradle 8.0 onwards and Gradle 8.0 runs on JDK 8, then the plugin should target JRE8 when possible. This is a release engineering matter only, that which is published.
Will fork and re-roll a Java8 version under another GAV.
It is not clear what bytecode level feature is being utilised to require JRE11 at runtime, or if this was just the release engineering JDK used on the day of the release (no technical reason).
Previous releases 4.0.0 used Java8 bytecode, 4.1.0 appears to be using Java11 bytecode with Java8 features (i.e. no new Java 11 APIs are utilized). As a published plugin it is good to consider this area. You ideally want the support the oldest JDK at runtime that matches the oldest Gradle version it is compatible with, so if Gradle works then this plugin just works.
So if 4.1.0 is compatible with Gradle 8.0 onwards and Gradle 8.0 runs on JDK 8, then the plugin should target JRE8 when possible. This is a release engineering matter only, that which is published.
Will fork and re-roll a Java8 version under another GAV.
Feel free to close issue.