You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamás Cservenák (Jira)" <ji...@apache.org> on 2021/08/09 12:24:00 UTC
[jira] [Assigned] (MPLUGIN-372) Descriptor generation does not work
when Mojo class hierarchy extends provided class
[ https://issues.apache.org/jira/browse/MPLUGIN-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamás Cservenák reassigned MPLUGIN-372:
---------------------------------------
Assignee: Tamás Cservenák
> Descriptor generation does not work when Mojo class hierarchy extends provided class
> ------------------------------------------------------------------------------------
>
> Key: MPLUGIN-372
> URL: https://issues.apache.org/jira/browse/MPLUGIN-372
> Project: Maven Plugin Tools
> Issue Type: Task
> Components: maven-plugin-tools-annotations, Plugin Plugin
> Reporter: Tamás Cservenák
> Assignee: Tamás Cservenák
> Priority: Major
> Fix For: 3.6.2
>
>
> As part of work on MPLUGIN-370 took an example plugin (m-dependency-p) and just set its maven dependencies to provided. Build exploded with NoClassDefFoundEx (usually for AbstractMojo). Nb: error reporting could be improved, as even with debug output nothing is said why this happened.
> Reason is that DescriptorGeneratorMojo sets ResolutionScope.RUNTIME that **excludes** provided dependencies (like maven-plugin-api, where AbstractMojo is).
> Setting the descriptor mojo scope to ResolutionScope.COMPILE_PLUS_RUNTIME make it work just fine.
> Anyone have any idea why Descriptor Mojo uses RUNTIME scope (hence, omits provided artifacts from processing)?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)