[MPLUGIN-372] Descriptor generation does not work when Mojo class hierarchy extends provided class

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.6.2
• Component/s: maven-plugin-tools-annotations, Plugin Plugin
• Assignee: Tamas Cservenak
• Reporter: Tamas Cservenak
• Created: 28/Apr/21 12:03
• Updated: 29/Nov/21 23:41
• Resolved: 09/Aug/21 12:28

Description

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)?

Issue Links

• causes: MPLUGIN-382 Too many dependencies in plugin descriptor
• links to: GitHub Pull Request #33
• links to: GitHub Pull Request #35