You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/05/29 14:18:46 UTC
DO NOT REPLY [Bug 20326] New: -
{ENH] Logging: version id, significant events
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=20326>.
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=20326
{ENH] Logging: version id, significant events
Summary: {ENH] Logging: version id, significant events
Product: JMeter
Version: 1.9RC1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Main
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: jkb@stian.freeserve.co.uk
It might be useful if JMeter logged its version number each time it started.
It would probably also be useful if it logged certain other significant events,
such as number of threads, and start/end of entire test - but probably not much
more than that.
This could be done by using log.info().
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org