Update site (remove HttpUnit references).

Author: henryju

src/site/resources/images/jwebunit-architecture.odg

@@ -23,11 +23,8 @@
         <links>
             <item name="JUnit" href="http://www.junit.org" />
             <item name="Maven" href="http://maven.apache.org" />
-            <item name="HTTPUnit"
-                href="http://httpunit.sourceforge.net" />
             <item name="HTMLUnit"
                 href="http://htmlunit.sourceforge.net" />
-            <item name="Jacobie" href="http://jacobie.sourceforge.net" />
             <item name="Selenium" href="http://openqa.org/selenium-rc/" />
         </links>
         <menu name="jWebUnit">
@@ -56,15 +53,6 @@
             </item>
         </menu>
         <menu name="Building jWebUnit">
-            <item name="With Ant" href="/building-ant.html"
-                collapse="true">
-                <item name="Installing Ant"
-                    href="/building-ant.html#Installing_Ant" />
-                <item name="Building jWebUnit"
-                    href="/building-ant.html#Building_jWebUnit" />
-                <item name="Building a release"
-                    href="/building-ant.html#Building_a_release" />
-            </item>
             <item name="With Maven" href="/building-maven.html"
                 collapse="true">
                 <item name="Installing Maven"

src/site/resources/images/jwebunit-architecture.png

@@ -19,7 +19,7 @@
     <p>
         jWebUnit is a Java framework that facilitates creation of acceptance tests for web applications. It 
         evolved from a project where we were using <a href="http://www.junit.org">JUnit</a> to create acceptance tests. 
-        Also, we have different testing engines: <a href="jwebunit-httpunit-plugin/index.html">HttpUnit</a> and <a href="jwebunit-htmlunit-plugin/index.html">HtmlUnit</a>. 
+        Also, we can have different testing engines. Currently, only <a href="jwebunit-htmlunit-plugin/index.html">HtmlUnit plugin</a> is ready. 
         As the tests were being written, they were continuously refactored to remove duplication and other bad smells in the test 
         code. jWebUnit is the result of these refactorings.
     </p>
@@ -31,8 +31,8 @@
         via links, form entry and submission, validation of table contents, and other
         typical business web application features. This code try to stay independent of the libraries behind
         the scenes. The simple navigation methods and ready-to-use assertions allow for
-        more rapid test creation than using only JUnit and HttpUnit/HtmlUnit. And if you want to switch
-        from HttpUnit to HtmlUnit, no need to rewrite your tests.
+        more rapid test creation than using only JUnit and HtmlUnit. And if you want to switch
+        from HtmlUnit to the other soon available plugins, no need to rewrite your tests.
     </p>
     <img src="images/jwebunit-architecture.png" alt="JWebUnit architecture"/>
 </section>

src/site/site.xml

@@ -50,10 +50,9 @@
 	</subsection>
 	<subsection name="Choose what plugin you want to use">
 		<p>
-			There are currently 2 available plugins:
+			There are currently 1 available plugin:
 			<ul>
-				<li>HttpUnit: Was the first supported plugin. Javascript support is very basic. Will not be supported in jWebUnit 2.x</li>
-				<li>HtmlUnit: A good choice if you want better Javascript support.</li>
+				<li>HtmlUnit: A good choice if you want rapidity and good Javascript support.</li>
 			</ul>
 		</p>
 	</subsection>

src/site/xdoc/building-ant.xml

@@ -52,8 +52,7 @@ import net.sourceforge.jwebunit.TestingEngineRegistry;
 public class ExampleWebTestCase extends WebTestCase {
     public ExampleWebTestCase(String name) {
         super(name);
-        setTestingEngineKey(TestingEngineRegistry.TESTING_ENGINE_HTTPUNIT);
-        // or setTestingEngineKey(TestingEngineRegistry.TESTING_ENGINE_HTMLUNIT);
+        setTestingEngineKey(TestingEngineRegistry.TESTING_ENGINE_HTMLUNIT);
     }
 }
 </source>