Re: (jmeter) branch master updated: chore: set next version to 6.0.0
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
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 suggests always using three components (e.g. see 2.0.0 at > semver.org) > > > > WDYT? > > > > Vladimir > > > > -- Cordialement. Philippe Mouawad.
Re: (jmeter) branch master updated: chore: set next version to 6.0.0
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
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
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 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 d3cba66416 chore: set next version to 6.0.0 d3cba66416 is described below commit d3cba664160eeb8c856e6f2281bcbd12f09546f6 Author: Vladimir Sitnikov AuthorDate: Tue Jan 9 11:00:48 2024 +0300 chore: set next version to 6.0.0 --- gradle.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gradle.properties b/gradle.properties index eda4cfba05..83166e07ac 100644 --- a/gradle.properties +++ b/gradle.properties @@ -34,7 +34,7 @@ systemProp.sonar.gradle.skipCompile=true # This is version for Apache JMeter itself # Note: it should not include "-SNAPSHOT" as it is automatically added by build.gradle.kts # Release version can be generated by using -Prelease or -Prc= arguments -jmeter.version=5.6.3 +jmeter.version=6.0.0 # Plugins com.github.vlsi.checksum-dependency.sha512=FAC41BF54A7C833BEAE9AB64083F6BEB3E1935BD6866C1B2F1D48FF926ABA4AECA53600FC3E41BE6ECBC87B73CE12F59C59836FB2E1DECC9408288060D66E988
[I] The counter used in the script recording has assigned a variable name for one http request [jmeter]
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 a format
string naming scheme and set counter to 001 and when all actions in the script
are complete I will see a sequence of http requests in numerical order.
Format used is #{counter,number,000} - #{path} (#{name})
### Actual behavior
The sequence was correct until it got to 443 - instead of writing:
"443 - /usrsvcs etc etc" I got this:
"${PORT} - /usrsvcs etc etc".
All of the numbers up to and after 443 are correct.
I happen to have a User defined Variable in my test plan with name 'PORT'
and value of 443.
### Steps to reproduce the problem
Create Test Plan
Add User Defined Variables with entry: 'PORT' and value 443
Add Recording Controller
Add HTTP Test Script Recorder and naming scheme is use Format String:
#{counter,number,000} - #{path} (#{name})
Add View Results Tree
start recording website activity such that you get at least 443 http
transactions. I would suggest using some sort of mapping application that
generates a lot of requests.
Keep an eye on the Recording Controller and see whether request 443 is named
differently from its neighbours.
### JMeter Version
5.6.2
### Java Version
Oracle JDK 17.0.2
### OS Version
Windows 10 10.0.19045 Build 19045
--
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.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [I] Cursor position in test plan changes jmx file [jmeter]
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`, probably all elements have their default values saved, see what was saved for the test plan).  `enabled=true` disappears only for the elements that were selected, i.e. when you open a test plan, select some elements and save, then the elements you selected were saved without `enabled=true` the other were saved with `enabled=true`. This is complication for the development because you see the changes you haven’t done upon the commit. Every time the test plan is loaded then a default value is appended to all elements. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Cursor position in test plan changes jmx file [jmeter]
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 @@ -27,7 +27,7 @@ - + 1 1 true @@ -38,7 +38,7 @@ - + true GET true ``` -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Cursor position in test plan changes jmx file [jmeter]
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. ### Actual behavior Outputed jmx file is different based on the cursor position while saving the test plan. It is hard to track changes of jmx file because of this. ### Steps to reproduce the problem Open the attached sample test plan then select Thread Group and save the plan (or you can just try to close JMeter application and you will be notified that there are some changes in the test plan) and compare the outputed file with the original one, you will see the differences. Different position of the cursor in the test plan produces different output. [sample.zip](https://github.com/apache/jmeter/files/13872087/sample.zip) ### JMeter Version 5.6.3 ### Java Version _No response_ ### OS Version _No response_ -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] change: use Java 17 as the build target, require Java 17+ for execution [jmeter]
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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
