jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Milamber <milam...@apache.org>
Subject Re: Renaming NON GUI mode into CLI mode
Date Fri, 15 Feb 2019 07:15:05 GMT


On 14/02/2019 18:55, Philippe Mouawad wrote:
> If I modify
> https://github.com/apache/jmeter/blob/trunk/src/core/org/apache/jmeter/JMeter.java#L368
>
> Is it a problem ?


With the cancel of RC1 result, you can modify this file for an include 
into RC2. Ping me after.



> Thanks
>
> On Thu, Feb 14, 2019 at 6:44 PM Milamber <milamber@apache.org> wrote:
>
>> You can change the trunk and after I will backport on docs-5.1 branch to
>> publish in a second time.
>>
>> On 14/02/2019 18:36, Philippe Mouawad wrote:
>>> Unless there is a no go I’d like to commit docs modification that I’d
>> like
>>> to be published with 5.1 release.
>>>
>>> Can I proceed ?
>>>
>>> Thanks
>>>
>>>
>>> On Tuesday, February 12, 2019, Milamber <milamber@apache.org> wrote:
>>>
>>>> On 12/02/2019 14:31, Philippe Mouawad wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> What do you think or replacing or adding everywhere Non GUI  is
>> mentioned
>>>>> the "CLI  mode" notion ?
>>>>>
>>>>> Indeed, if you look at concurrent load test tools (OSS or Commerical),
>>>>> they
>>>>> all use the Cli mode notion, and use this argument as being a plus for
>>>>> automation.
>>>>>
>>>>> Non GUI mode notion for JMeter is not meaningful for non jmeter users.
>>>>> I know in a previous proposal, Milamber wrote it was not really CLI.
>>>>> But IMO, if we compare it to other tool that use this notion, it is
>> CLI.
>>>>> So why loose another good argument to select JMeter by keeping this Non
>>>>> GUI
>>>>> thing ?
>>>>>
>>>> The non GUI mode is more a "batch mode" than a CLI mode, but I'm not
>>>> against to rename it if it's would better to understand for new users.
>>>>
>>>>
>>>>
>>>>
>>>>> Thoughts ?
>>>>> Regards
>>>>> Philippe
>>>>>
>>>>>
>>


Mime
View raw message