You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/01/10 10:58:00 UTC

[jira] [Commented] (MNG-7388) Support Java prerequisites for Maven plugins

    [ https://issues.apache.org/jira/browse/MNG-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471870#comment-17471870 ] 

Michael Osipov commented on MNG-7388:
-------------------------------------

But this isn't just only the plugin, isn't it? Same applies to dependencies. I wonder whether an enforcer rule can do this. Analyze class version of plugin. Maybe it comes too late.

> Support Java prerequisites for Maven plugins
> --------------------------------------------
>
>                 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)