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

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

     [ https://issues.apache.org/jira/browse/MPLUGIN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MPLUGIN-305.
----------------------------------
       Resolution: Fixed
         Assignee: Robert Scholte
    Fix Version/s: 3.5

Fixed in [r1754998|http://svn.apache.org/viewvc?rev=1754998&view=rev] by introducing a new parameter: mojoDependencies.

- not specified ( = null; default ) scan all dependencies
- {{<mojoDependencies/>}} , empty list, scan nothing.
- {{<mojoDependencies><mojoDependency>groupId:artifactId</mojoDependency><mojoDependencies>}}, scan only groupId:artifactId  dependency.

> 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
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: 3.5
>
>
> 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



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