[
https://issues.apache.org/jira/browse/MPLUGIN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417641#comment-15417641
]
Paul Benedict commented on MPLUGIN-305:
---------------------------------------
Recommendation to update this page:
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html
Addition to this sentence in bold: "Provided that the super class also uses
annotations, it can now come from reactor projects or external dependencies.
*You specify these dependencies by using the {{mojoDependencies}} property.*"
> 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)
