Re: MQTT Sampler

Is there really a sufficient use case that we need to include it in core? How many developers are familiar with the protocol and can maintain the code and answer user queries? On 2 February 2016 at 22:49, Philippe Mouawad wrote: > Hi , > Any thoughts on this ? > > Thanks > > On Monday, January 2

Re: Regarding Groovy Bundling - Groovy now a TLP

There is as yet only an incubating release. I think we need to wait for an official ASF release. On 2 February 2016 at 22:51, Philippe Mouawad wrote: > Hi Team, > Any thoughts on that ? > Thx > > On Wednesday, January 13, 2016, Pascal Schumacher > wrote: > >> Am 13.01.2016 um 20:03 schrieb Phil

Re: svn commit: r1725955 - in /jmeter/trunk: ./ lib/ licenses/bin/ res/maven/ src/functions/org/apache/jmeter/functions/ test/src/org/apache/jmeter/functions/ xdocs/ xdocs/usermanual/

I fixed it although tag is not clear for me On Thursday, January 21, 2016, sebb wrote: > On 21 January 2016 at 20:32, Philippe Mouawad > > wrote: > > On Thu, Jan 21, 2016 at 9:19 PM, sebb > > wrote: > > > >> On 21 January 2016 at 14:10, > > wrote: > >> > Author: pmouawad > >> > Date: Thu Jan 21

Re: Regarding Groovy Bundling - Groovy now a TLP

Hi Team, Any thoughts on that ? Thx On Wednesday, January 13, 2016, Pascal Schumacher wrote: > Am 13.01.2016 um 20:03 schrieb Philippe Mouawad: > >> @Pascal, as we now target java7 , what bundle should we use if this is >> agreed on by other team members ? >> > With Java 7 you could use the groo

Re: About latency computation

Hi, Any thoughts on that ? Thx On Wednesday, January 13, 2016, Philippe Mouawad wrote: > Hello, > I think we should fix our computing of latency property. > > AFAIU when I look at HTTPHC4Impl: > >- sampleStart : there is some processing that occurs after it is >called: > - There is

Re: Switch "jmeter.save.saveservice.assertion_results_failure_message" to true by default

I am for it. I have made this the default for my service and think it is valuable in all responses. The only issue, it is breaking to anyone who built around the default. Kind of goes to 3.0 or not. If 3.0 then this is a breaking change and ok. In a minor release, would be against it. Rich On T

Re: Release a 3.0

Hi, If this is to block next release, then I will go for a 2.14 although I think that this numbering makes people think JMeter is only releasing minor fixes and think they don't have to upgrade. Please sebb, can you give your final thought ? thankd Regards Philippe On Monday, January 25, 2016,

Re: MQTT Sampler

Hi , Any thoughts on this ? Thanks On Monday, January 25, 2016, Philippe Mouawad wrote: > Hello, > As you know we received a PR request for MQTT sampler. > Before we go further (contact the forked MQTT Sampler project to know if > they agree to provide it to core, I think it is necessary no ?),

Re: Switch "jmeter.save.saveservice.assertion_results_failure_message" to true by default

Hi, Any thoughts on that ? Can I proceed? Thanks On Thursday, January 28, 2016, Philippe Mouawad < p.moua...@ubik-ingenierie.com> wrote: > Hello, > Report/Dashboard feature requires this property to be saved to be able to > build correctly the Errors table. > > Indeed if this property is false, t

Build failed in Jenkins: JMeter-trunk #4932

See Changes: [pmouawad] Misc clean up rename variables remove commented code remove outdated comments #resolve #101 [pmouawad] Bug 58897 - Improve JUnit Test code #resolve #100 Bugzilla Id: 58897 [pmouawad] Bug 58897 - Improve JUnit Test

[GitHub] jmeter pull request: Misc clean up

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/101 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] jmeter pull request: Bug 58897 : Step 4 convert existing tests

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/100 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] jmeter pull request: Fixes #58957

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/103 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] jmeter pull request: Fixes 58884

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/102 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] jmeter pull request: Fixes #58957

GitHub user ubikfsabbe opened a pull request: https://github.com/apache/jmeter/pull/103 Fixes #58957 https://bz.apache.org/bugzilla/show_bug.cgi?id=58957 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ubikfsabbe/jmeter bug-58957

[GitHub] jmeter pull request: Fixes 58884

GitHub user ubikfsabbe opened a pull request: https://github.com/apache/jmeter/pull/102 Fixes 58884 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ubikfsabbe/jmeter bug-58884 Alternatively you can review and apply these changes

[GitHub] jmeter pull request: Misc clean up

GitHub user benbenw opened a pull request: https://github.com/apache/jmeter/pull/101 Misc clean up rename variables remove commented code remove outdated comments You can merge this pull request into a Git repository by running: $ git pull https://github.com/benbenw/jme