Port configuration of the (undocumented) jsunit goal of the javascript-maven-plugin appears to be broken

The jsunit goal of the javascript-maven-plugin (version 1.0-alpha-1-SNAPSHOT) is undocumented (here: http://mojo.codehaus.org/javascript-maven-tools/javascript-maven-plugin/index.html). However, browsing the plugin metadata one can see that a port attribute can be configured to control the port upon which the JsUnitServer spawned by the plugin listens for the submission of test results from the browser(s).

There is an inconsistency because although the port attribute does indeed control the port at which the JsUnitServer listens for results, it has no effect upon the port to which the browser submits them!

This is a fairly serious problem as we wish to use the plugin in our CI tool, Hudson, which runs out of Tomcat which is already using port 8080. I'd guess this is a common scenario.

I have submitted a fairly trivial patch to fix it. Recent experience confirms that it works.