Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #102350 +++ As mentioned in the cloned bug, we _do_ have a utility to trace "out going http requests" during JUnit tests ... but, I think, it has to be manually copied to our JREs lib/ext directory when ever we get a new JRE and that has not been done for a while. I could "just do it" ... but, probably should not, final week before Juno M2 ... just in case there's some side effect that breaks the build. Plus, worth noting ... should integrate logs into JUnit page. Plus, given this has gone undetected for a long time, perhaps add a "releng test" that tests for the presence/absence of the httphandler jar (or, more easy, to make sure there is _some_ output, and if not, assume the test is broken). Then we could "flag an error" to remind us to copy over the httphandler.jar.
Whew, done. I did create a new version of jar, in proper "eclipse.org" namespace. Put in in the appropriate JRE's lib/ext directory. The change in namespace required a change to builder. Plus, I changed builder to copy logs from "test" location to the committers download location, and "hooked in" the reports to the normal JUnit summary page (next to similar console log reports). I tested on test build machine, and all looked fine. Should show up in future builds on build.eclipse.org. I only updated files/scripts for the JSDT builds, WTP builds, and WTP4x builds. I only updated builder tag for "head" releng build.cfg ... guess maintenance can be updated if/when desired ... or, when other changes are made there. Most important, I added a wiki page (to update the old description on website ... the old website URL was http://www.eclipse.org/webtools/development/httptracerutility/index.php which I left there, marked as "deprecated"). The new wiki page is at http://wiki.eclipse.org/WTP/HTTP_Connection_Tracer_Diagnostic_Utility
