From 3ed2aef1df4fb0fa650bfe79714b2a35b0cd9446 Mon Sep 17 00:00:00 2001 From: Herve Boutemy Date: Sat, 20 Jul 2013 22:14:54 +0000 Subject: [PATCH] [MPLUGIN-246] Clarify that super class must also use annotations git-svn-id: https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1505228 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/site/apt/examples/using-annotations.apt.vm | 2 +- 1 file changed, 1 insertion(+), 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 07f8b95..7347b96 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 @@ -30,7 +30,7 @@ Using Plugin Tools Java5 Annotations Since version 3.0, you can use Java5 annotations to generate the plugin descriptor file. - <> With annotations, it's not any more mandatory to have your Mojos super classes in the same project. Super classes + <> 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).