Fix a few things detected during the release.

Author: henryju

pom.xml

@@ -283,7 +283,14 @@
                 <plugin>
                     <groupId>org.apache.maven.plugins</groupId>
                     <artifactId>maven-site-plugin</artifactId>
-                    <version>3.1</version>
+                    <version>3.2</version>
+                    <dependencies>
+                        <dependency><!-- add support for ssh/scp -->
+                            <groupId>org.apache.maven.wagon</groupId>
+                            <artifactId>wagon-ssh</artifactId>
+                            <version>1.0</version>
+                        </dependency>
+                    </dependencies>
                 </plugin>
                 <plugin>
                     <groupId>org.apache.maven.plugins</groupId>
@@ -573,7 +580,7 @@
             <id>jwebunit-website</id>
             <name>JWebUnit WebSite - Sourceforge</name>
             <url>
-                scp://web.sourceforge.net/home/project-web/jwebunit/htdocs
+                scp://shell.sourceforge.net/home/project-web/jwebunit/htdocs
             </url>
         </site>
         <snapshotRepository>

src/changes/changes.xml

@@ -47,8 +47,6 @@
             <action type="update" dev="henryju">
                 Deprecated gotoWindow(windowID) method as implementation is not stable and window ID is not something well-defined.
             </action>
-        </release>
-        <release version="3.0.1" date="UNKNOW" description="Minor fixes">
             <action type="fix" dev="henryju" issue="3395872" due-to="Tim Pizey">
                 HtmlUnitTestingEngineImpl.gotoPage no longer returns the failing status. Broken since 2.5 after applying
                 patch from issue 1864365.

src/site/xdoc/how-to-release.xml

@@ -69,19 +69,21 @@
             <subsection name="Preparing the release (tag and update pom)">
                 <p>
                     This process is automatically done by maven-release-plugin.
-                    <source>mvn release:prepare -Dusername=henryju -Dpassword=XXXXXX</source>
-                    Don't forget to put your own sourceforge account and password.<br/>
+                    <source>mvn release:prepare</source>
                     The plugin will ask for next release version, tag name and next development version. Most of the time defaults are ok.<br/>
-                    <em>NB:</em> Sometimes with SVN 1.5 the tag operation fails with a message like <tt>file XXX already exists</tt>. The solution is
-                    to run <tt>svn update</tt> then run <tt>mvn release:prepare -Dusername=henryju -Dpassword=XXXXXX</tt> again.
                 </p>
                 <p>
                     Now the tag is done in SVN and the trunk is ready for next developments. It's time to actually do the release.
                 </p>
             </subsection>
             <subsection name="Perform the release (deploy artifacts and site)">
-               	<p>
-                    The process is done by maven-release-plugin.
+                <p>
+                    Create a shell on sourceforge (<a href="http://maven.apache.org/plugins/maven-site-plugin/examples/site-deploy-to-sourceforge.net.html">more informations</a>).
+                    <source>ssh -t henryju,jwebunit@shell.sf.net create</source>
+                    Then exit the shell (type exit).
+                </p>
+                <p>
+                    The release process is done by maven-release-plugin:
                     <source>mvn release:perform -Darguments="-Dgpg.passphrase=XXXXXXXXXX"</source>
                 </p>
                 <p>