stephenc
/
maven-plugin-tools
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

Improve documentation

git-svn-id: https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1756022 13f79535-47bb-0310-9956-ffa450edef68
master
Robert Scholte 2016-08-11 18:07:18 +00:00
parent 372526b052
commit 7c58d51900
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm
View File

@ -32,9 +32,10 @@ Using Plugin Tools Java5 Annotations
plugin descriptor file. plugin descriptor file.
<<NOTE>> With annotations, your Mojo super class does not any more require to be in the same project. Provided that the super class also uses annotations, it <<NOTE>> With annotations, your Mojo super class does not any more require to be in the same project. Provided that the super class also uses annotations, it
can now come from reactor projects or external dependencies. As javadoc doclet are still useful for <<<@since>>>, <<<@deprecated>>> and comments, can now come from reactor projects or external dependencies. By default all dependencies are scanned, but this can be reduced with the <<<mojoDependencies>>>
the sources are still scanned. So if you use an external dependency, you must still provide an artifact with sources (<<<sources>>> classifier) to parameter. As javadoc doclet are still useful for <<<@since>>>, <<<@deprecated>>> and comments, the sources are still scanned. So if you use an external
provide documentation (the tooling will skip error if this artifact sources is missing). dependency, you must still provide an artifact with sources (<<<sources>>> classifier) to provide documentation (the tooling will skip error if this artifact
sources is missing).
* Annotations * Annotations