[jira] [Created] (MPLUGIN-305) MojoAnnotationsScanner should have better control over dependency scanning

["Robert Scholte (JIRA)" <ji...@apache.org>]

Robert Scholte created MPLUGIN-305:
--------------------------------------

             Summary: MojoAnnotationsScanner should have better control over dependency scanning
                 Key: MPLUGIN-305
                 URL: https://issues.apache.org/jira/browse/MPLUGIN-305
             Project: Maven Plugin Tools
          Issue Type: Improvement
          Components: maven-plugin-tools-annotations
            Reporter: Robert Scholte
            Priority: Minor


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)