[MPLUGIN-305] MojoAnnotationsScanner should have better control over dependency scanning

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.5
• Component/s: maven-plugin-tools-annotations
• Assignee: Robert Scholte
• Reporter: Robert Scholte
• Created: 19/Jul/16 20:59
• Updated: 06/Jan/18 01:57
• Resolved: 02/Aug/16 19:40

Description

Currently MojoAnnotationsScanner always scans all dependencies in search for Mojo's. However, most of the time there's no need to do so: the sources are all the mojo's for the plugin.
The simple solution would be to specify if the plugin should scan, and maybe even which dependencies.
A more elegant way would be to analyze the source-classes. If the Mojo's extend known classes like AbstractMojo, there's no need to scan at all.

ps. plugins which require dependencies-scanning are the maven-surefire-plugin and maven-failsafe-plugin

Issue Links

• is related to: MPLUGIN-328 ArrayIndexOutOfBoundsException: 48188
• relates to: MPLUGIN-330 If and else-if branches has the same condition
• supercedes: MPLUGIN-291 Provide toggle to enable mojo detection for dependencies