hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10816] - User/Developer Documentation
Date Thu, 26 Jun 2003 11:20:24 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10816>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10816

User/Developer Documentation

adrian@ephox.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |commons-httpclient-
                   |                            |dev@jakarta.apache.org
         AssignedTo|commons-httpclient-         |adrian@ephox.com
                   |dev@jakarta.apache.org      |



------- Additional Comments From adrian@ephox.com  2003-06-26 11:20 -------
We now have a license for clover to use with HttpClient (HttpClient committers 
can email me for details on how to get their hands on it).  To add the report 
to the website we need to specify it as a report in the project.xml.  However, 
it means that we have to specify every report we want to run so we won't 
automatically get any new reports that are added to maven's default setup.  I 
have listed all the reports we currently have in the project.xml.

Also, for clover to work, you must run the unit tests in a forked JVM as the 
results are only written out when the JVM exits.  I've added the property that 
achieves this to project.properties, but if you rebuild httpclient using maven 
a lot during development, you may wish to override this in your own 
build.properties (which takes precedence).  The line to add is:

maven.junit.fork=false

Also, the clover plugin seems to have major issues on Windows, particularly 
when there is a space in the path to the HttpClient sources.  I'm not sure if 
this has been fixed in maven's CVS yet or not.

So, do considering these down sides, do we wish to add clover to maven's 
default run or should we:

a. add a link to the report via navigation.xml and run the clover report 
manually then upload it to the site.

b. Not put the clover report on the website and just use it when required.

c. Go find a fix for the problems and use an updated version of the clover 
plugin when generating the site (what happens to anyone who is still using the 
last stable release of maven or before?).

d.  Something completely different.

Mime
View raw message