Author: hboutemy
Date: Sat Jul 20 22:14:54 2013
New Revision: 1505228
URL: http://svn.apache.org/r1505228
Log:
[MPLUGIN-246] Clarify that super class must also use annotations
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm
URL:
http://svn.apache.org/viewvc/maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm?rev=1505228&r1=1505227&r2=1505228&view=diff
==============================================================================
---
maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm
(original)
+++
maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm
Sat Jul 20 22:14:54 2013
@@ -30,7 +30,7 @@ Using Plugin Tools Java5 Annotations
Since version 3.0, you can use Java5 annotations to generate the plugin
descriptor file.
- <<NOTE>> With annotations, it's not any more mandatory to have your Mojos
super classes in the same project. Super classes
+ <<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,
the sources are still scanned. So if you use an external 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).
