From 250f72677d84437a7df81bb3c472a9954243a9fb Mon Sep 17 00:00:00 2001 From: Karl Heinz Marbaise Date: Sat, 21 May 2016 10:11:58 +0000 Subject: [PATCH] [MPLUGIN-301] Text improvement. git-svn-id: https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1744886 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/site/apt/examples/using-annotations.apt.vm | 3 ++- 1 file changed, 2 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 5dacf0e..823d776 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 @@ -28,7 +28,8 @@ Using Plugin Tools Java5 Annotations - Since version 3.0, you can use Java5 annotations to generate the plugin descriptor file. + Since version 3.0 of the maven-plugin-plugin, you can use Java5 annotations to generate the + 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,