Bug 63616 - Java Doc - JMeterContext getThreadNum start at 0 and not 1
Summary: Java Doc - JMeterContext getThreadNum start at 0 and not 1
Status: RESOLVED FIXED
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: unspecified
Hardware: All All
: P2 trivial (vote)
Target Milestone: JMETER_5.2
Assignee: JMeter issues mailing list
URL:
Keywords: FixedInTrunk
Depends on:
Blocks:
 
Reported: 2019-07-28 05:40 UTC by orimarko
Modified: 2019-07-28 08:09 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description orimarko 2019-07-28 05:40:12 UTC
JMeterContext getThreadNum start at 0 and not 1,
Doc:
@return the threadNum starting from one

Should be 
@return the threadNum starting from zero
Comment 1 Philippe Mouawad 2019-07-28 08:09:53 UTC
This is an automated email from the ASF dual-hosted git repository.

pmouawad pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jmeter.git


The following commit(s) were added to refs/heads/master by this push:
     new cfcc5e1  Bug 63616: Java Doc - JMeterContext getThreadNum start at 0 and not 1
cfcc5e1 is described below

commit cfcc5e1d3548041b5dbf612b34b4650d3cbd82c0
Author: pmouawad <p.mouawad@ubik-ingenierie.com>
AuthorDate: Sun Jul 28 10:08:45 2019 +0200

    Bug 63616: Java Doc - JMeterContext getThreadNum start at 0 and not 1

    https://bz.apache.org/bugzilla/show_bug.cgi?id=63616
    This resolves Bug 63616
---
 src/core/org/apache/jmeter/threads/JMeterContext.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)