From 3a52298a040f20e6c2ddb983320e34376a264cb7 Mon Sep 17 00:00:00 2001 From: Olivier Lamy Date: Sat, 19 May 2012 07:10:52 +0000 Subject: [PATCH] improve note on super classes when using annotations for sources git-svn-id: https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1340364 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/site/apt/examples/using-annotations.apt.vm | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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 a67ddb7..4c83d17 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 @@ -31,7 +31,9 @@ Using Java5 annotations Since version 3.0, you can use {{{#Annotations}Java5 annotations}} to generate the plugin descriptor file. <> With annotations, it's not anymore mandatory to have your Mojos super classes in the same project. Super classe - can now come from reactor projects or external dependencies. + can now come from reactor projects or external dependencies. As javadoc doclet are still reading (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 sources) to + provide documentation (the tooling will skip error if this artifact sources is missing). * Pom configuration