You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2016/07/19 21:03:20 UTC

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

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

Robert Scholte updated MPLUGIN-305:
-----------------------------------
    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

  was:
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.


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