Re: (jmeter) branch master updated: chore: set next version to 6.0.0

2024-01-09 Thread Ralf Roeber
three digits - fine with me. Happy that this popped up and thanks for asking. Am 1/9/2024 um 6:21 PM schrieb Vladimir Sitnikov: semver suggests always using three components (e.g. see 2.0.0 at semver.org) WDYT? Vladimir Ralf

Re: (jmeter) branch master updated: chore: set next version to 6.0.0

2024-01-09 Thread Philippe Mouawad
Hello, Fine for me. Regards On Tue, Jan 9, 2024 at 7:03 PM Milamber wrote: > > No special issue to have 3 digits, just want keep same logic as other > JMeter major release. > If PMC members are agree with 3 digits, I am ok too. > > > On 09/01/2024 18:21, Vladimir Sitnikov wrote: > > semver

Re: (jmeter) branch master updated: chore: set next version to 6.0.0

2024-01-09 Thread Milamber
No special issue to have 3 digits, just want keep same logic as other JMeter major release. If PMC members are agree with 3 digits, I am ok too. On 09/01/2024 18:21, Vladimir Sitnikov wrote: semver suggests always using three components (e.g. see 2.0.0 at semver.org) WDYT? Vladimir

Re: (jmeter) branch master updated: chore: set next version to 6.0.0

2024-01-09 Thread Vladimir Sitnikov
semver suggests always using three components (e.g. see 2.0.0 at semver.org) WDYT? Vladimir

Re: (jmeter) branch master updated: chore: set next version to 6.0.0

2024-01-09 Thread Milamber
Hi Vladimir, Generally next major version of JMeter was with only 2 digits : 6.0 without last .0. Can you change to 6.0 pls. Milamber. On 09/01/2024 09:12, vladimirsitni...@apache.org wrote: This is an automated email from the ASF dual-hosted git repository. vladimirsitnikov pushed a

[I] The counter used in the script recording has assigned a variable name for one http request [jmeter]

2024-01-09 Thread via GitHub
Danbown opened a new issue, #6222: URL: https://github.com/apache/jmeter/issues/6222 ### Expected behavior This is a minor issue for me but but unexpected, since it casts doubt on the logic used for this function. I expect to record a test script with Test Script Recorder and use

Re: [I] Cursor position in test plan changes jmx file [jmeter]

2024-01-09 Thread via GitHub
koudela5 commented on issue #6221: URL: https://github.com/apache/jmeter/issues/6221#issuecomment-1883170067 I see the opposite. When you open "sample.jmx" and then immediately save the file you will see something what you can see on the screenshot (every single element has `enabled=true`,

Re: [I] Cursor position in test plan changes jmx file [jmeter]

2024-01-09 Thread via GitHub
vlsi commented on issue #6221: URL: https://github.com/apache/jmeter/issues/6221#issuecomment-1882866557 The diff is that `enabled=true` appears only for the currently selected element ```diff --- sample2.jmx 2024-01-09 14:04:16 +++ sample3.jmx 2024-01-09 14:03:44

[I] Cursor position in test plan changes jmx file [jmeter]

2024-01-09 Thread via GitHub
koudela5 opened a new issue, #6221: URL: https://github.com/apache/jmeter/issues/6221 ### Expected behavior If you save a JMeter plan with no changes in the test plan then outputed jmx file is still same no matter where you had the cursor while saving the test plan. ###

Re: [PR] change: use Java 17 as the build target, require Java 17+ for execution [jmeter]

2024-01-09 Thread via GitHub
vlsi merged PR #6220: URL: https://github.com/apache/jmeter/pull/6220 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org