Port configuration of the (undocumented) jsunit goal of the
javascript-maven-plugin appears to be broken
--------------------------------------------------------------------------------------------------------
Key: MJS-33
URL: http://jira.codehaus.org/browse/MJS-33
Project: Maven Javascript Tools
Issue Type: Bug
Reporter: Philip McWilliams
Attachments: JsUnitMojoPatch.txt
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
