[GitHub] jmeter pull request: rename variables for clarity

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/142


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: Remove commented code

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/154


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: drop some deprecated methods

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/149


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: remove dead code 2

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/146


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: remove dead code

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/145


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: [59105] TableEditor: add from clipboard

[pmouawad]

Github user pmouawad commented on the pull request:

https://github.com/apache/jmeter/pull/153#issuecomment-192499523
  
Thanks for contribution !
In my opinion, no need for an additional property unless you think there 
might be a bug.
Could you provide a Test Plan with some components you tested that use this 
component (except Compare Assertion) ?

At team member, feel free to merge it, I will be waiting the plan.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: PR for BUG 59116 without tab

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/158


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: Bug 59118 - Add comment in recorded thik time...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/157


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

@Mark,
A short term option would be to invite those who wants from JMeter team to
have admin rights on the github repository so that your project has a
bigger community.

I personally would be interested, I do not promise to be an important
contributor but I'll do my best.


Regards

On Friday, March 4, 2016, Philippe Mouawad 
wrote:

>
>
> On Friday, March 4, 2016, sebb  > wrote:
>
>> On 4 March 2016 at 10:38, Mark Collin 
>> wrote:
>> > If the JMeter devs want to put it in core I have no issue with that,
>> however the plugin is a maven project an I don’t think maven projects are
>> wanted in JMeter core :)
>>
>> JMeter does not use Maven as its build tool.
>> It would be a major effort to convert to Maven, so it's not going to
>> be done just in order to support a Maven plugin.
>> If indeed it is ever done (but that is another discussion).
>>
>> However the plugin clearly does not have to be part of the same source
>> tree / build process as JMeter (it's not currently).
>> I think it is better for it to have an entirely separate release
>> process, as it is not only affected by the JMeter version.
>> It's going to be far more dependent on Maven changes.
>>
>> Whether or not it is sensible for the JMeter project to own / maintain
>> the code is another matter.
>> I think not, because JMeter is usable with lots of other build / test
>> tools, and is usable stand-alone.
>>
>> It does not make sense for the JMeter project to maintain plugins for
>> all the possible tools.
>> If we take on a Maven plugin, then how about Groovy, Jenkins,
>> Buildbot, Gradle etc?
>> This does not scale. Furthermore, the code most needs Maven developer
>> expertise, not JMeter expertise.
>
>
>
> If Mark is ok with this, what about having a separate sister project of
> jmeter for the maven plugin (maybe also the jenkins one if we have some
> volunteers)
> It could be (if incubated and agreed upon) under the Apache umbrella and
> we could(those who want) participate to it.
>
> The release process would be partly dependant on jmeter but as sebb wrote
> also on maven /jenkins.
>
>
>
>
>
>>
>> > The website is down at the moment, it’s in the process of being moved
>> over to github.io. (I should probably update the README to note that)
>> >
>> >> On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues 
>> wrote:
>> >>
>> >> Hi Mark,
>> >>
>> >> I don't have problem with JMeter-Maven-Plugin (and your documentation
>> >> rocks) in particularity
>> >>
>> >> It's only my experience with third party plugin in general and project
>> with
>> >> only one developer.
>> >> And this experience is not always good and it's why I don't like to
>> advise
>> >> my customer to use these projects/plugins
>> >>
>> >> One question, why don't integrate officially your plugin to JMeter
>> core?
>> >>
>> >> About your website, I have a timeout :-(
>> >>
>> >> Thanks to your feedback
>> >>
>> >> Antonio
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
>> >> www.avast.com
>> >> <
>> https://www.avast.com/fr-fr/lp-esg-win-01a?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-C
>> >
>> >> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> >>
>> >> 2016-03-04 9:29 GMT+01:00 Mark Collin :
>> >>
>> >>>
>> >> Lack of official feature (JMeter plugin, Maven plugin, etc.)
>> >
>> >
>> > non official maven plugin exists and works rather nicely.
>> > What do you mean by JMeter plugin ?
>> >
>> 
>>  In general I have very bad experience with:
>>  third party plugin (not well integrate, not well tested, not up to
>> date
>>  with the latest release, etc.)
>>  Plugin maintained by only one person (less motivation by the
>> developer,
>>  etc.)
>> >>>
>> >>> Bug fixes for the maven plugin are happily accepted.  Also please add
>> >>> issues for things that are:
>> >>> Not well integrated
>> >>> Not well tested
>> >>> Not up to date
>> >>> So that we can fix them (
>> >>> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>> >>>
>> >>> In regards to it being up to date:
>> >>> The plugin didn’t support JMeter 2.12 Because there were transitive
>> >>> dependency issues with the 2.12 maven release.
>> >>> There were also transitive dependency issues with the JMeter 2.13
>> release
>> >>> that we tried to work around.  Version 1.10.1 of the plugin does use
>> JMeter
>> >>> 2.13.
>> >>> Is there something else we have missed which makes you say it’s not
>> up to
>> >>> date (Feedback is the only way we can make it better)?
>> >>>
>> >>> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
>> >>> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype
>> snapshots
>> >>> repository if you want to try it out and provide some 

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

On Friday, March 4, 2016, sebb  wrote:

> On 4 March 2016 at 10:38, Mark Collin  > wrote:
> > If the JMeter devs want to put it in core I have no issue with that,
> however the plugin is a maven project an I don’t think maven projects are
> wanted in JMeter core :)
>
> JMeter does not use Maven as its build tool.
> It would be a major effort to convert to Maven, so it's not going to
> be done just in order to support a Maven plugin.
> If indeed it is ever done (but that is another discussion).
>
> However the plugin clearly does not have to be part of the same source
> tree / build process as JMeter (it's not currently).
> I think it is better for it to have an entirely separate release
> process, as it is not only affected by the JMeter version.
> It's going to be far more dependent on Maven changes.
>
> Whether or not it is sensible for the JMeter project to own / maintain
> the code is another matter.
> I think not, because JMeter is usable with lots of other build / test
> tools, and is usable stand-alone.
>
> It does not make sense for the JMeter project to maintain plugins for
> all the possible tools.
> If we take on a Maven plugin, then how about Groovy, Jenkins,
> Buildbot, Gradle etc?
> This does not scale. Furthermore, the code most needs Maven developer
> expertise, not JMeter expertise.



If Mark is ok with this, what about having a separate sister project of
jmeter for the maven plugin (maybe also the jenkins one if we have some
volunteers)
It could be (if incubated and agreed upon) under the Apache umbrella and we
could(those who want) participate to it.

The release process would be partly dependant on jmeter but as sebb wrote
also on maven /jenkins.





>
> > The website is down at the moment, it’s in the process of being moved
> over to github.io. (I should probably update the README to note that)
> >
> >> On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues  > wrote:
> >>
> >> Hi Mark,
> >>
> >> I don't have problem with JMeter-Maven-Plugin (and your documentation
> >> rocks) in particularity
> >>
> >> It's only my experience with third party plugin in general and project
> with
> >> only one developer.
> >> And this experience is not always good and it's why I don't like to
> advise
> >> my customer to use these projects/plugins
> >>
> >> One question, why don't integrate officially your plugin to JMeter core?
> >>
> >> About your website, I have a timeout :-(
> >>
> >> Thanks to your feedback
> >>
> >> Antonio
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> >> www.avast.com
> >> <
> https://www.avast.com/fr-fr/lp-esg-win-01a?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-C
> >
> >> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >>
> >> 2016-03-04 9:29 GMT+01:00 Mark Collin  >:
> >>
> >>>
> >> Lack of official feature (JMeter plugin, Maven plugin, etc.)
> >
> >
> > non official maven plugin exists and works rather nicely.
> > What do you mean by JMeter plugin ?
> >
> 
>  In general I have very bad experience with:
>  third party plugin (not well integrate, not well tested, not up to
> date
>  with the latest release, etc.)
>  Plugin maintained by only one person (less motivation by the
> developer,
>  etc.)
> >>>
> >>> Bug fixes for the maven plugin are happily accepted.  Also please add
> >>> issues for things that are:
> >>> Not well integrated
> >>> Not well tested
> >>> Not up to date
> >>> So that we can fix them (
> >>> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
> >>>
> >>> In regards to it being up to date:
> >>> The plugin didn’t support JMeter 2.12 Because there were transitive
> >>> dependency issues with the 2.12 maven release.
> >>> There were also transitive dependency issues with the JMeter 2.13
> release
> >>> that we tried to work around.  Version 1.10.1 of the plugin does use
> JMeter
> >>> 2.13.
> >>> Is there something else we have missed which makes you say it’s not up
> to
> >>> date (Feedback is the only way we can make it better)?
> >>>
> >>> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
> >>> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype
> snapshots
> >>> repository if you want to try it out and provide some feedback so that
> we
> >>> can make it better that would be really useful.
> >
>


-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hi Mark,
I confirm your project is up to date and very well documented and the work
you're doing is great,
Thanks !

As you know the 3.0 is close to a release, it would be great if you could
confirm that dependencies management is ok this time.

If you could do that when we start the release process it would be even
better.

Regards


On Friday, March 4, 2016, Mark Collin  wrote:

>
> >>> Lack of official feature (JMeter plugin, Maven plugin, etc.)
> >>
> >>
> >> non official maven plugin exists and works rather nicely.
> >> What do you mean by JMeter plugin ?
> >>
> >
> > In general I have very bad experience with:
> > third party plugin (not well integrate, not well tested, not up to date
> > with the latest release, etc.)
> > Plugin maintained by only one person (less motivation by the developer,
> > etc.)
>
> Bug fixes for the maven plugin are happily accepted.  Also please add
> issues for things that are:
> Not well integrated
> Not well tested
> Not up to date
> So that we can fix them (
> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>
> In regards to it being up to date:
> The plugin didn’t support JMeter 2.12 Because there were transitive
> dependency issues with the 2.12 maven release.
> There were also transitive dependency issues with the JMeter 2.13 release
> that we tried to work around.  Version 1.10.1 of the plugin does use JMeter
> 2.13.
> Is there something else we have missed which makes you say it’s not up to
> date (Feedback is the only way we can make it better)?
>
> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots
> repository if you want to try it out and provide some feedback so that we
> can make it better that would be really useful.



-- 
Cordialement.
Philippe Mouawad.

[GitHub] jmeter pull request: Bug 59116

[ra0077]

Github user ra0077 closed the pull request at:

https://github.com/apache/jmeter/pull/156


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: Bug 59116

[ra0077]

Github user ra0077 commented on the pull request:

https://github.com/apache/jmeter/pull/156#issuecomment-192354635
  
Problem with tab


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: PR for BUG 59116 without tab

[benbenw]

Github user benbenw commented on the pull request:

https://github.com/apache/jmeter/pull/158#issuecomment-192354414
  
you should close the previous PR (156).


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jmeter pull request: PR for BUG 59116 without tab

[ra0077]

GitHub user ra0077 opened a pull request:

https://github.com/apache/jmeter/pull/158

PR for BUG 59116 without tab

Hi,


I have add a new option in proxy recorder to add a prefix in sampler name 
recorded by the proxy.

It allow to be more productive (less work to rename samplers after a 
recording) and complete the regex in backend listener I have add previously

This new PR fix the tab

Antonio

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ra0077/jmeter 
Bug59116_ProxyRecorderHTTPNamePrefix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jmeter/pull/158.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #158


commit 8e384c8850432b5b128a078430ee4289852c1bea
Author: ra0077 
Date:   2016-03-04T16:38:06Z

PR for BUG 59116 without tab




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Remaining Work before Release of 3.0

[sebb]

On 4 March 2016 at 10:38, Mark Collin  wrote:
> If the JMeter devs want to put it in core I have no issue with that, however 
> the plugin is a maven project an I don’t think maven projects are wanted in 
> JMeter core :)

JMeter does not use Maven as its build tool.
It would be a major effort to convert to Maven, so it's not going to
be done just in order to support a Maven plugin.
If indeed it is ever done (but that is another discussion).

However the plugin clearly does not have to be part of the same source
tree / build process as JMeter (it's not currently).
I think it is better for it to have an entirely separate release
process, as it is not only affected by the JMeter version.
It's going to be far more dependent on Maven changes.

Whether or not it is sensible for the JMeter project to own / maintain
the code is another matter.
I think not, because JMeter is usable with lots of other build / test
tools, and is usable stand-alone.

It does not make sense for the JMeter project to maintain plugins for
all the possible tools.
If we take on a Maven plugin, then how about Groovy, Jenkins,
Buildbot, Gradle etc?
This does not scale. Furthermore, the code most needs Maven developer
expertise, not JMeter expertise.

> The website is down at the moment, it’s in the process of being moved over to 
> github.io. (I should probably update the README to note that)
>
>> On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues  wrote:
>>
>> Hi Mark,
>>
>> I don't have problem with JMeter-Maven-Plugin (and your documentation
>> rocks) in particularity
>>
>> It's only my experience with third party plugin in general and project with
>> only one developer.
>> And this experience is not always good and it's why I don't like to advise
>> my customer to use these projects/plugins
>>
>> One question, why don't integrate officially your plugin to JMeter core?
>>
>> About your website, I have a timeout :-(
>>
>> Thanks to your feedback
>>
>> Antonio
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
>> www.avast.com
>> 
>> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> 2016-03-04 9:29 GMT+01:00 Mark Collin :
>>
>>>
>> Lack of official feature (JMeter plugin, Maven plugin, etc.)
>
>
> non official maven plugin exists and works rather nicely.
> What do you mean by JMeter plugin ?
>

 In general I have very bad experience with:
 third party plugin (not well integrate, not well tested, not up to date
 with the latest release, etc.)
 Plugin maintained by only one person (less motivation by the developer,
 etc.)
>>>
>>> Bug fixes for the maven plugin are happily accepted.  Also please add
>>> issues for things that are:
>>> Not well integrated
>>> Not well tested
>>> Not up to date
>>> So that we can fix them (
>>> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>>>
>>> In regards to it being up to date:
>>> The plugin didn’t support JMeter 2.12 Because there were transitive
>>> dependency issues with the 2.12 maven release.
>>> There were also transitive dependency issues with the JMeter 2.13 release
>>> that we tried to work around.  Version 1.10.1 of the plugin does use JMeter
>>> 2.13.
>>> Is there something else we have missed which makes you say it’s not up to
>>> date (Feedback is the only way we can make it better)?
>>>
>>> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
>>> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots
>>> repository if you want to try it out and provide some feedback so that we
>>> can make it better that would be really useful.
>

[GitHub] jmeter pull request: Bug 59118 - Add comment in recorded thik time...

[ra0077]

GitHub user ra0077 opened a pull request:

https://github.com/apache/jmeter/pull/157

Bug 59118 - Add comment in recorded thik time by proxy recorder

Hi,

To complete my previous PR about adding a new template "recording with
think time" I have made a new PR.

This PR add a comment in the recorded timer like "Recorded think time:
XXXms"

It will allow to:
   differentiate recorded timer from other
   have the original think time duration

Antonio

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ra0077/jmeter AddCommentsInThinkTimeRecorded

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jmeter/pull/157.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #157


commit e2589591e78f8664fa0a98d77ee5b95efee4c040
Author: ra0077 
Date:   2016-03-04T15:13:15Z

Bug 59118 - Add comment in recorded thik time by proxy recorder

Hi,

To complete my previous PR about adding a new template "recording with
think time" I have made a new PR.

This PR add a comment in the recorded timer like "Recorded think time:
XXXms"

It will allow to:
   differentiate recorded timer from other
   have the original think time duration

Antonio




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: https://ci.apache.org/projects/jmeter/nightlies/ : NIghtly build not generated since 16th january

[sebb]

On 4 March 2016 at 06:38, Philippe Mouawad  wrote:
> On Friday, March 4, 2016, sebb  wrote:
>
>> On 3 March 2016 at 22:14, Philippe Mouawad > > wrote:
>> > On Thu, Mar 3, 2016 at 11:05 PM, sebb >
>> wrote:
>> >
>> >> On 3 March 2016 at 21:51, Philippe Mouawad > >
>> >> wrote:
>> >> > On Thu, Mar 3, 2016 at 10:47 PM, sebb > > wrote:
>> >> >
>> >> >> On 2 March 2016 at 21:04, Philippe Mouawad <
>> philippe.moua...@gmail.com >
>> >> >> wrote:
>> >> >> > Thanks
>> >> >> > My questions inline
>> >> >> >
>> >> >> > On Wed, Mar 2, 2016 at 2:32 PM, sebb > > wrote:
>> >> >> >
>> >> >> >> This is part of buildbot
>> >> >> >>
>> >> >> >> https://ci.apache.org/
>> >> >> >
>> >> >> >
>> >> >> > How do you change the build ?
>> >> >>
>> >> >> By editting the config files.
>> >> >>
>> >> >
>> >> > You fixed it today ? I received a message saying build was back to
>> >> normal.
>> >>
>> >> The nightly build is still broken
>> >>
>> >> https://ci.apache.org/builders/jmeter-nightly
>> >>
>> >> Trunk is mostly OK
>> >>
>> >> https://ci.apache.org/builders/jmeter-trunk
>> >>
>> >> I have committed a fix for the headless failures, but it has not yet
>> >> been picked up.
>> >> I'll have to prod Infra.
>> >>
>> >
>> > Ok, thanks
>>
>> It looks like all the nightly builds stopped on that date.
>>
>> >>
>> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> The code is under:
>> >> >> >>
>> >> >> >> https://svn.apache.org/repos/infra/infrastructure/buildbot
>> >> >> >
>> >> >> >
>> >> >> > I don't have the rights to access it.
>> >> >>
>> >> >> It's probably restricted to infra and infra assistants.
>> >> >>
>> >> >> What exactly needs changing?
>> >> >>
>> >> >
>> >> > It should match the new nightly.xml content since 2 days ago we
>> started
>> >> > distributing the bundle instead of lib and bin.
>> >>
>> >> What should match?
>> >>
>> >> The description of bundles in trunk is ok, in bot
>> > https://svn.apache.org/repos/infra/infrastructure/buildbot it is wrong.
>> > You can read the nightly.xml in trunk.
>>
>> No idea what you are talking about.
>>
>> Please provide full URLs to the pages, and say what needs to be
>> changed if it's not obvious.
>
>
> when 3.0 will be released this page will contain the up to date doc:
> https://jmeter.apache.org/nightly.html , see in xdocs/nightly.xml the new
> content

Since the builds have already changed, the online docs ought really to
be updated please.

> and this one will be wrong:
> https://ci.apache.org/projects/jmeter/nightlies/

OK, understood.

I have made some changes, however the page is built by a process that
does not seem to have run since Jan 16.
So waiting on Infra to fix/restart it.

>
>
>
>
>>
>> >> >
>> >> >
>> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> On 1 March 2016 at 21:58, Philippe Mouawad <
>> >> philippe.moua...@gmail.com >
>> >> >> >> wrote:
>> >> >> >> > Hi,
>> >> >> >> > Any clue on this ?
>> >> >> >> >
>> >> >> >> > Anybody knows how it works and where we can update the nightly
>> page
>> >> >> that
>> >> >> >> > displays ?
>> >> >> >> > Thanks
>> >> >> >> >
>> >> >> >> > On Sun, Feb 28, 2016 at 10:27 PM, Philippe Mouawad <
>> >> >> >> > philippe.moua...@gmail.com > wrote:
>> >> >> >> >
>> >> >> >> >> Hello,
>> >> >> >> >> How do we fix this ?
>> >> >> >> >> Where is it configured ?
>> >> >> >> >>
>> >> >> >> >> Thanks for help
>> >> >> >> >> Regards
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Cordialement.
>> >> >> >> > Philippe Mouawad.
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cordialement.
>> >> >> > Philippe Mouawad.
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cordialement.
>> >> > Philippe Mouawad.
>> >>
>> >
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.

[GitHub] jmeter pull request: Bug 59116

[ra0077]

GitHub user ra0077 opened a pull request:

https://github.com/apache/jmeter/pull/156

Bug 59116

Hi,


I have add a new option in proxy recorder to add a prefix in sampler
name recorded by the proxy.

It allow to be more productive (less work to rename samplers after a
recording) and complete the regex in backend listener I have add
previously

Antonio

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ra0077/jmeter ProxyRecorderHTTPNamePrefix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jmeter/pull/156.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #156


commit 49163c46678c031052b0190aa2eef713d52a85dc
Author: ra0077 
Date:   2016-03-04T14:39:01Z

Bug 59116

Hi,


I have add a new option in proxy recorder to add a prefix in sampler
name recorded by the proxy.

It allow to be more productive (less work to rename samplers after a
recording) and complete the regex in backend listener I have add
previously

Antonio




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Remaining Work before Release of 3.0

[Antonio Gomes Rodrigues]

Hi,

Anybody know if it's possible to add it?

If no, why?

Thank
Antonio

2016-03-04 11:38 GMT+01:00 Mark Collin :

> If the JMeter devs want to put it in core I have no issue with that,
> however the plugin is a maven project an I don’t think maven projects are
> wanted in JMeter core :)
>
> The website is down at the moment, it’s in the process of being moved over
> to github.io. (I should probably update the README to note that)
>
> > On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues 
> wrote:
> >
> > Hi Mark,
> >
> > I don't have problem with JMeter-Maven-Plugin (and your documentation
> > rocks) in particularity
> >
> > It's only my experience with third party plugin in general and project
> with
> > only one developer.
> > And this experience is not always good and it's why I don't like to
> advise
> > my customer to use these projects/plugins
> >
> > One question, why don't integrate officially your plugin to JMeter core?
> >
> > About your website, I have a timeout :-(
> >
> > Thanks to your feedback
> >
> > Antonio
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> > www.avast.com
> > <
> https://www.avast.com/fr-fr/lp-esg-win-01a?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-C
> >
> > <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > 2016-03-04 9:29 GMT+01:00 Mark Collin :
> >
> >>
> > Lack of official feature (JMeter plugin, Maven plugin, etc.)
> 
> 
>  non official maven plugin exists and works rather nicely.
>  What do you mean by JMeter plugin ?
> 
> >>>
> >>> In general I have very bad experience with:
> >>> third party plugin (not well integrate, not well tested, not up to date
> >>> with the latest release, etc.)
> >>> Plugin maintained by only one person (less motivation by the developer,
> >>> etc.)
> >>
> >> Bug fixes for the maven plugin are happily accepted.  Also please add
> >> issues for things that are:
> >> Not well integrated
> >> Not well tested
> >> Not up to date
> >> So that we can fix them (
> >> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
> >>
> >> In regards to it being up to date:
> >> The plugin didn’t support JMeter 2.12 Because there were transitive
> >> dependency issues with the 2.12 maven release.
> >> There were also transitive dependency issues with the JMeter 2.13
> release
> >> that we tried to work around.  Version 1.10.1 of the plugin does use
> JMeter
> >> 2.13.
> >> Is there something else we have missed which makes you say it’s not up
> to
> >> date (Feedback is the only way we can make it better)?
> >>
> >> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
> >> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype
> snapshots
> >> repository if you want to try it out and provide some feedback so that
> we
> >> can make it better that would be really useful.
>
>

Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: Remaining Work before Release of 3.0

[Mark Collin]

If the JMeter devs want to put it in core I have no issue with that, however 
the plugin is a maven project an I don’t think maven projects are wanted in 
JMeter core :)

The website is down at the moment, it’s in the process of being moved over to 
github.io. (I should probably update the README to note that)

> On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues  wrote:
> 
> Hi Mark,
> 
> I don't have problem with JMeter-Maven-Plugin (and your documentation
> rocks) in particularity
> 
> It's only my experience with third party plugin in general and project with
> only one developer.
> And this experience is not always good and it's why I don't like to advise
> my customer to use these projects/plugins
> 
> One question, why don't integrate officially your plugin to JMeter core?
> 
> About your website, I have a timeout :-(
> 
> Thanks to your feedback
> 
> Antonio
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> www.avast.com
> 
> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> 2016-03-04 9:29 GMT+01:00 Mark Collin :
> 
>> 
> Lack of official feature (JMeter plugin, Maven plugin, etc.)
 
 
 non official maven plugin exists and works rather nicely.
 What do you mean by JMeter plugin ?
 
>>> 
>>> In general I have very bad experience with:
>>> third party plugin (not well integrate, not well tested, not up to date
>>> with the latest release, etc.)
>>> Plugin maintained by only one person (less motivation by the developer,
>>> etc.)
>> 
>> Bug fixes for the maven plugin are happily accepted.  Also please add
>> issues for things that are:
>> Not well integrated
>> Not well tested
>> Not up to date
>> So that we can fix them (
>> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>> 
>> In regards to it being up to date:
>> The plugin didn’t support JMeter 2.12 Because there were transitive
>> dependency issues with the 2.12 maven release.
>> There were also transitive dependency issues with the JMeter 2.13 release
>> that we tried to work around.  Version 1.10.1 of the plugin does use JMeter
>> 2.13.
>> Is there something else we have missed which makes you say it’s not up to
>> date (Feedback is the only way we can make it better)?
>> 
>> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
>> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots
>> repository if you want to try it out and provide some feedback so that we
>> can make it better that would be really useful.

Re: Remaining Work before Release of 3.0

[Antonio Gomes Rodrigues]

Hi Mark,

I don't have problem with JMeter-Maven-Plugin (and your documentation
rocks) in particularity

It's only my experience with third party plugin in general and project with
only one developer.
And this experience is not always good and it's why I don't like to advise
my customer to use these projects/plugins

One question, why don't integrate officially your plugin to JMeter core?

About your website, I have a timeout :-(

Thanks to your feedback

Antonio









Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2016-03-04 9:29 GMT+01:00 Mark Collin :

>
> >>> Lack of official feature (JMeter plugin, Maven plugin, etc.)
> >>
> >>
> >> non official maven plugin exists and works rather nicely.
> >> What do you mean by JMeter plugin ?
> >>
> >
> > In general I have very bad experience with:
> > third party plugin (not well integrate, not well tested, not up to date
> > with the latest release, etc.)
> > Plugin maintained by only one person (less motivation by the developer,
> > etc.)
>
> Bug fixes for the maven plugin are happily accepted.  Also please add
> issues for things that are:
> Not well integrated
> Not well tested
> Not up to date
> So that we can fix them (
> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>
> In regards to it being up to date:
> The plugin didn’t support JMeter 2.12 Because there were transitive
> dependency issues with the 2.12 maven release.
> There were also transitive dependency issues with the JMeter 2.13 release
> that we tried to work around.  Version 1.10.1 of the plugin does use JMeter
> 2.13.
> Is there something else we have missed which makes you say it’s not up to
> date (Feedback is the only way we can make it better)?
>
> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots
> repository if you want to try it out and provide some feedback so that we
> can make it better that would be really useful.

[GitHub] jmeter pull request: Bug 52073 Embedded Resources concurrent downl...

[benbenw]

GitHub user benbenw opened a pull request:

https://github.com/apache/jmeter/pull/155

Bug 52073 Embedded Resources concurrent download : Improve performances by 
avoiding shutdown of ThreadPoolExecutor at each sample.


A shared thread pool is used for all the parallel downloads.
A throttle mechanism is used per user to ensure the max concurrent
downloads setting is not exceeded.
A new parameter httpsampler.parallel_download_thread_keepalive_inseconds
is used to set the thread TTL when idle (default 60s).
the parameter httpsampler.await_termination_timeout is not used anymore
and has been removed.

TODO : ResourcesDownloader#shrink should be called at the end of a test
to accelerate the release of the thread pool idle threads (not
mandatory)

the httpclient is shared between the threads of a given virtual user.
the cache is shared between the threads of a given virtual user.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/benbenw/jmeter resdownload3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jmeter/pull/155.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #155


commit e5ac1cf4dcfb578444766300e9bc5005168acc46
Author: benoit 
Date:   2016-02-17T22:46:36Z

Bug 52073 Embedded Resources concurrent download : Improve performances
by avoiding shutdown of ThreadPoolExecutor at each sample.

A shared thread pool is used for all the parallel downloads.
A throttle mechanism is used per user to ensure the max concurrent
downloads setting is not exceeded.
A new parameter httpsampler.parallel_download_thread_keepalive_inseconds
is used to set the thread TTL when idle (default 60s).
the parameter httpsampler.await_termination_timeout is not used anymore
and has been removed.

TODO : ResourcesDownloader#shrink should be called at the end of a test
to accelerate the release of the thread pool idle threads (not
mandatory)

the httpclient is shared between the threads of a given virtual user.
the cache is shared between the threads of a given virtual user.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Remaining Work before Release of 3.0

[Mark Collin]

>>> Lack of official feature (JMeter plugin, Maven plugin, etc.)
>> 
>> 
>> non official maven plugin exists and works rather nicely.
>> What do you mean by JMeter plugin ?
>> 
> 
> In general I have very bad experience with:
> third party plugin (not well integrate, not well tested, not up to date
> with the latest release, etc.)
> Plugin maintained by only one person (less motivation by the developer,
> etc.)

Bug fixes for the maven plugin are happily accepted.  Also please add issues 
for things that are:
Not well integrated
Not well tested
Not up to date
So that we can fix them 
(https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).

In regards to it being up to date:
The plugin didn’t support JMeter 2.12 Because there were transitive dependency 
issues with the 2.12 maven release.
There were also transitive dependency issues with the JMeter 2.13 release that 
we tried to work around.  Version 1.10.1 of the plugin does use JMeter 2.13.
Is there something else we have missed which makes you say it’s not up to date 
(Feedback is the only way we can make it better)?

We are planning a version 2.0.0 of the plugin to coincide with a 3.0 JMeter 
release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots repository 
if you want to try it out and provide some feedback so that we can make it 
better that would be really useful.