From 7c58d51900c3def4bd110aaacfd27c895d5ac851 Mon Sep 17 00:00:00 2001 From: Robert Scholte Date: Thu, 11 Aug 2016 18:07:18 +0000 Subject: [PATCH] [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 --- .../src/site/apt/examples/using-annotations.apt.vm | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm b/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm index 823d776..8a710dc 100644 --- a/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm +++ b/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm @@ -32,9 +32,10 @@ Using Plugin Tools Java5 Annotations plugin descriptor file. <> 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, - the sources are still scanned. So if you use an external dependency, you must still provide an artifact with sources (<<>> classifier) to - provide documentation (the tooling will skip error if this artifact sources is missing). + can now come from reactor projects or external dependencies. By default all dependencies are scanned, but this can be reduced with the <<>> + parameter. As javadoc doclet are still useful for <<<@since>>>, <<<@deprecated>>> and comments, the sources are still scanned. So if you use an external + dependency, you must still provide an artifact with sources (<<>> classifier) to provide documentation (the tooling will skip error if this artifact + sources is missing). * Annotations