[MJAR-127] Deprecate jarsigner related goals in favor of dedicated maven-jarsigner-plugin
o Cleaned up documentation
git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk@979824 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/src/site/apt/usage.apt.vm b/src/site/apt/usage.apt.vm
index 4beea4e..ef65c43 100644
--- a/src/site/apt/usage.apt.vm
+++ b/src/site/apt/usage.apt.vm
@@ -33,6 +33,10 @@
configurations you should have a look at the documentation for
{{{http://maven.apache.org/shared/maven-archiver/}Maven Archiver}}.
+ Note: Originally, this plugin was meant to sign JARs as well. As of version 2.3, the corresponding goals are no
+ longer supported and users are advised to use the dedicated
+ {{{http://maven.apache.org/plugins/maven-jarsigner-plugin/}Maven Jarsigner Plugin}} instead.
+
* How to build a jar file
If the packaging of your project is set to 'jar', this plugin is executed
@@ -45,70 +49,6 @@
In your project's <<<target>>> directory you'll able to see the generated jar file.
-
-* How to sign a jar file
-
- If you need to sign your jar, you just need to configure
- the sign goal appropriately in your <<<pom.xml>>>, for the signing to occur
- automatically during the package phase.
-
- Note that you can automatically verify a jar after signing it.
-
-+-----------------+
-<project>
- ...
- <packaging>jar</packaging>
- ...
- <build>
- <plugins>
- ...
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-jar-plugin</artifactId>
- <version>${project.version}</version>
- <executions>
- <execution>
- <goals>
- <goal>sign</goal>
- </goals>
- </execution>
- </executions>
- <configuration>
- <keystore>/path/to/your/keystore</keystore>
- <alias>youralias</alias>
- <storepass>yourstorepassword</storepass>
- <signedjar>\${project.build.directory}/signed/\${project.build.finalName}.jar</signedjar>
- <verify>true</verify>
- </configuration>
- </plugin>
- ...
- </plugins>
- </build>
- ...
-</project>
-+-----------------+
-
- If you do not specify the <<<\<signedjar\>>>> file, your jar will be signed in-place.
- If you do specify it, the plugin will attempt to create the resulting containing directory.
-
-* How to sign a jar file specifying parameters on the command line
-
-+-----------------+
-mvn jar:sign -Dkeystore=/path/to/your/keystore -Dstorepass=yourstorepassword -Dalias=youralias
-+-----------------+
-
-* How to verify a signed jar file specifying parameters on the command line
-
-+-----------------+
-mvn jar:sign-verify [-Djarpath=/path/to/your/signedjar] [-Dverbose=true [-Dcheckcerts=true] ]
-+-----------------+
-
-* How to disable jar signing
-
-+-----------------+
-mvn ... -Dmaven.jar.skip.sign=true
-+-----------------+
-
* How to include/exclude content from jar artifact
Specify a list of fileset patterns to be included or excluded by adding