Skip to content

Commit b3f427e

Browse files
authored
Remove decade+ old content (#265)
3.0.0 was in 2012.
1 parent 668f6c0 commit b3f427e

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,9 @@
2828

2929
Using Plugin Tools Java Annotations
3030

31-
Since version 3.0 of the maven-plugin-plugin, you can use Java5 annotations to generate the
32-
plugin descriptor file.
31+
You can use Java annotations to generate the plugin descriptor file.
3332

34-
<<NOTE>> With annotations, your Mojo super class does not have to be in the same project: provided that the super class also uses annotations, it
33+
<<NOTE>> With annotations, your Mojo super class does not have to be in the same project: provided that the superclass also uses annotations, it
3534
can now come from reactor projects or external dependencies. By default all dependencies are scanned, but this can be reduced with the <<<mojoDependencies>>>
3635
parameter. BUT as javadoc doclets are still useful for goals and parameters description, <<<@since>>> and <<<@deprecated>>>, the sources are still scanned. So if you use an external
3736
dependency, you must still provide an artifact with sources (<<<sources>>> classifier) to provide documentation (the tooling will skip error if this artifact
@@ -79,8 +78,8 @@ Using Plugin Tools Java Annotations
7978

8079
* POM configuration
8180

82-
To be able to use these Java annotations, you need to add to your plugin POM
83-
<<<maven-plugin-annotations>>> dependency, preferably with <<<provided>>> scope.
81+
To use these Java annotations, add a dependency on
82+
<<<maven-plugin-annotations>>> to your pom, preferably with <<<provided>>> scope.
8483

8584
+-----+
8685
<project>

0 commit comments

Comments
 (0)