[
https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471805#comment-17471805
]
Konrad Windszus edited comment on MNG-7388 at 1/10/22, 9:39 AM:
----------------------------------------------------------------
IMHO with the separation of Build vs Consumer you should have a dedicated
consumer element. Also `maven.compiler.target` is not evaluated at run time
(i.e. when executing the plugin) and is IMHO just a plugin configuration (i.e.
stripped for consumers).
was (Author: kwin):
IMHO with the separation of Build vs Consumer you should have a dedicated
consumer element. Also `maven.compiler.target` is not evaluated at run time
(i.e. when executing the plugin).
> Support Java prerequisites for packaging "maven-plugin"
> -------------------------------------------------------
>
> Key: MNG-7388
> URL: https://issues.apache.org/jira/browse/MNG-7388
> Project: Maven
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently only the minimum Maven version can be explicitly required for a
> Maven plugin via {{prerequisites->maven}}. The same should be possible for
> the Java version, as Maven plugins compiled for Java 11 won't run on Java 8
> and currently only emit the nasty "UnsupportedClassVersion" errors.
> The plugin reporting plugin uses some heuristics in
> https://github.com/apache/maven-plugin-tools/blob/c6d0808b92423b969f8d2aac500b7263399d0373/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java#L739,
> but this is only considered for the plugin documentation but never at run
> time.
> This requires a Maven model change though, and therefore can only end up in
> Maven 5.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
