[RESULT] [VOTE] Release JMeter 3.2 RC3

[Milamber]

Hello,

Thanks very much to all who voted for this release.

The votes were as follows:

=== +1 vote (with *: binding) ===

Philippe Mouawad (pmouawad)*
Andrey Pokhilko (undera)
Maxime Chassagneux (mchassagneux)
Christophe Dumont
Antonio Gomes Rodrigues (agomes)*
Felix Schumacher (fschumacher)*
NaveenKumar Namachivayam
Bruno Demion (milamber)*

===

There were no other votes, so the vote passes.

I will prepare the delivery of release for having an official announce
after the mirrors sync.

Milamber


On 09/04/2017 17:31, Milamber wrote:

Hello,

The third release candidate for JMeter 3.2 (r1790748) has been 
prepared, and your votes are solicited.


This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional 
tests) using Java 8 on Linux/Windows/Mac OS, especially on the 
changes. The feedback are welcome.


You can read the New and Noteworthy section with some screenshots to 
illustrate improvements and full list of changes at:

http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html

JMeter is a Java desktop application designed to load test functional 
behavior and measure performance. The current version is targeted at 
Java 8+.


Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
(dist revision r19091)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt 



MD5 hashes of archives for this vote:

04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/ 



Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds 




All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

Re: [VOTE] Release JMeter 3.2 RC3

[NaveenKumar Namachivayam]

+1


Get Outlook for iOS






On Thu, Apr 13, 2017 at 2:45 AM -0500, "Milamber"  wrote:











My vote : +1

On 09/04/2017 17:31, Milamber wrote:
> Hello,
>
> The third release candidate for JMeter 3.2 (r1790748) has been 
> prepared, and your votes are solicited.
>
> This release brings new features and fixes bugs.
>
> Please, test this release candidate (with load tests and/or functional 
> tests) using Java 8 on Linux/Windows/Mac OS, especially on the 
> changes. The feedback are welcome.
>
> You can read the New and Noteworthy section with some screenshots to 
> illustrate improvements and full list of changes at:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
>
> JMeter is a Java desktop application designed to load test functional 
> behavior and measure performance. The current version is targeted at 
> Java 8+.
>
> Download - Archives/hashes/sigs:
>
> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
> (dist revision r19091)
>
> RAT report:
>
> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt
>  
>
>
> MD5 hashes of archives for this vote:
>
> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
>
> Site Docs are here:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
>
> Maven staging repository is accessible here:
> https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/
>  
>
>
> Tag:
> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
>
> Keys are here:
> https://www.apache.org/dist/jmeter/KEYS
>
> N.B.
> To download the dependencies: "ant download_jars"
>
> To create the jars and test JMeter: "ant package test".
>
> JMeter 3.2 requires Java 8 or later to run.
>
> Some known issues and incompatible changes are listed on changes page.
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds
>  
>
>
>
> All feedback and vote are welcome.
>
> [  ] +1  I support this release
> [  ] +0  I am OK with this release
> [  ] -0   OK, but
> [  ] -1   I do not support this release (please indicate why)
>
> The vote will remain open for at least 72 hours.
>
> The PMC members please indicate the mention "(binding)" with your vote.
>
>
> Note: If the vote passes, the intention is to release the archive files
> and rename the RC tag as the release tag.
>
> Thanks in advance!
>
> Milamber
>
>
>
>
>
>
>

Re: [VOTE] Release JMeter 3.2 RC3

[Philippe Mouawad]

[+1] We support this release.

Thank you for taking into account the reported issue with RC2

Thanks to RM !
Regards

On Thursday, April 13, 2017, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

>
>
> Am 9. April 2017 18:31:50 MESZ schrieb Milamber  >:
> >Hello,
> >
> >The third release candidate for JMeter 3.2 (r1790748) has been
> >prepared,
> >and your votes are solicited.
> >
> >This release brings new features and fixes bugs.
> >
> >Please, test this release candidate (with load tests and/or functional
> >tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
> >
> >The feedback are welcome.
> >
> >You can read the New and Noteworthy section with some screenshots to
> >illustrate improvements and full list of changes at:
> >http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
> >
> >JMeter is a Java desktop application designed to load test functional
> >behavior and measure performance. The current version is targeted at
> >Java 8+.
> >
> >Download - Archives/hashes/sigs:
> >
> >https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
> >(dist revision r19091)
> >
> >RAT report:
> >
> >http://home.apache.org/~milamber/jmeter-3.2RC3/dist/
> rat-report-jmeter-3.2RC3.txt
> >
> >MD5 hashes of archives for this vote:
> >
> >04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
> >a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
> >28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
> >d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
> >
> >Site Docs are here:
> >http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
> >
> >Maven staging repository is accessible here:
> >https://repository.apache.org/content/repositories/
> orgapachejmeter-1017/org/apache/jmeter/
> >
> >Tag:
> >https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
> >
> >Keys are here:
> >https://www.apache.org/dist/jmeter/KEYS
> >
> >N.B.
> >To download the dependencies: "ant download_jars"
> >
> >To create the jars and test JMeter: "ant package test".
> >
> >JMeter 3.2 requires Java 8 or later to run.
> >
> >Some known issues and incompatible changes are listed on changes page.
> >http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
> changes.html#Known%20problems%20and%20workarounds
> >
> >
> >All feedback and vote are welcome.
> >
> >[x] +1  I support this release
> >[  ] +0  I am OK with this release
> >[  ] -0   OK, but
> >[  ] -1   I do not support this release (please indicate why)
>
> Felix
>
> >
> >The vote will remain open for at least 72 hours.
> >
> >The PMC members please indicate the mention "(binding)" with your vote.
> >
> >
> >Note: If the vote passes, the intention is to release the archive files
> >and rename the RC tag as the release tag.
> >
> >Thanks in advance!
> >
> >Milamber
>


-- 
Cordialement.
Philippe Mouawad.

Re: [VOTE] Release JMeter 3.2 RC3

[Felix Schumacher]

Am 9. April 2017 18:31:50 MESZ schrieb Milamber :
>Hello,
>
>The third release candidate for JMeter 3.2 (r1790748) has been
>prepared, 
>and your votes are solicited.
>
>This release brings new features and fixes bugs.
>
>Please, test this release candidate (with load tests and/or functional 
>tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
>
>The feedback are welcome.
>
>You can read the New and Noteworthy section with some screenshots to 
>illustrate improvements and full list of changes at:
>http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
>
>JMeter is a Java desktop application designed to load test functional 
>behavior and measure performance. The current version is targeted at 
>Java 8+.
>
>Download - Archives/hashes/sigs:
>
>https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
>(dist revision r19091)
>
>RAT report:
>
>http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt
>
>MD5 hashes of archives for this vote:
>
>04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
>a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
>28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
>d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
>
>Site Docs are here:
>http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
>
>Maven staging repository is accessible here:
>https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/
>
>Tag:
>https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
>
>Keys are here:
>https://www.apache.org/dist/jmeter/KEYS
>
>N.B.
>To download the dependencies: "ant download_jars"
>
>To create the jars and test JMeter: "ant package test".
>
>JMeter 3.2 requires Java 8 or later to run.
>
>Some known issues and incompatible changes are listed on changes page.
>http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds
>
>
>All feedback and vote are welcome.
>   
>[x] +1  I support this release
>[  ] +0  I am OK with this release
>[  ] -0   OK, but
>[  ] -1   I do not support this release (please indicate why)

Felix

>
>The vote will remain open for at least 72 hours.
>
>The PMC members please indicate the mention "(binding)" with your vote.
>
>
>Note: If the vote passes, the intention is to release the archive files
>and rename the RC tag as the release tag.
>
>Thanks in advance!
>
>Milamber

Re: [VOTE] Release JMeter 3.2 RC3

[Antonio Gomes Rodrigues]

+1

Antonio

2017-04-13 10:20 GMT+02:00 Christophe Dumont :

> +1 
>
> 2017-04-13 10:05 GMT+02:00 Maxime Chassagneux <
> maxime.chassagn...@gmail.com>
> :
>
> > My vote : +1
> >
> > 2017-04-13 9:46 GMT+02:00 Milamber :
> >
> > >
> > > @PMC
> > >
> > > We need at least 3 '+1' votes from PMC members to allow this release.
> > > Currently we have only 2 +1.
> > >
> > >
> > > On 09/04/2017 17:31, Milamber wrote:
> > >
> > >> Hello,
> > >>
> > >> The third release candidate for JMeter 3.2 (r1790748) has been
> prepared,
> > >> and your votes are solicited.
> > >>
> > >> This release brings new features and fixes bugs.
> > >>
> > >> Please, test this release candidate (with load tests and/or functional
> > >> tests) using Java 8 on Linux/Windows/Mac OS, especially on the
> changes.
> > The
> > >> feedback are welcome.
> > >>
> > >> You can read the New and Noteworthy section with some screenshots to
> > >> illustrate improvements and full list of changes at:
> > >> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
> > >>
> > >> JMeter is a Java desktop application designed to load test functional
> > >> behavior and measure performance. The current version is targeted at
> > Java
> > >> 8+.
> > >>
> > >> Download - Archives/hashes/sigs:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
> > >> (dist revision r19091)
> > >>
> > >> RAT report:
> > >>
> > >> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-
> > >> report-jmeter-3.2RC3.txt
> > >>
> > >> MD5 hashes of archives for this vote:
> > >>
> > >> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
> > >> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
> > >> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
> > >> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
> > >>
> > >> Site Docs are here:
> > >> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
> > >>
> > >> Maven staging repository is accessible here:
> > >> https://repository.apache.org/content/repositories/orgapache
> > >> jmeter-1017/org/apache/jmeter/
> > >>
> > >> Tag:
> > >> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
> > >>
> > >> Keys are here:
> > >> https://www.apache.org/dist/jmeter/KEYS
> > >>
> > >> N.B.
> > >> To download the dependencies: "ant download_jars"
> > >>
> > >> To create the jars and test JMeter: "ant package test".
> > >>
> > >> JMeter 3.2 requires Java 8 or later to run.
> > >>
> > >> Some known issues and incompatible changes are listed on changes page.
> > >> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.
> > >> html#Known%20problems%20and%20workarounds
> > >>
> > >>
> > >> All feedback and vote are welcome.
> > >>
> > >> [  ] +1  I support this release
> > >> [  ] +0  I am OK with this release
> > >> [  ] -0   OK, but
> > >> [  ] -1   I do not support this release (please indicate why)
> > >>
> > >> The vote will remain open for at least 72 hours.
> > >>
> > >> The PMC members please indicate the mention "(binding)" with your
> vote.
> > >>
> > >>
> > >> Note: If the vote passes, the intention is to release the archive
> files
> > >> and rename the RC tag as the release tag.
> > >>
> > >> Thanks in advance!
> > >>
> > >> Milamber
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> >
>
>
>
> --
> Christophe Dumont
> Rue du Chapoteyre
> 38450 Miribel Lanchatre
> 0633475733
>

Re: [VOTE] Release JMeter 3.2 RC3

[Christophe Dumont]

+1 

2017-04-13 10:05 GMT+02:00 Maxime Chassagneux 
:

> My vote : +1
>
> 2017-04-13 9:46 GMT+02:00 Milamber :
>
> >
> > @PMC
> >
> > We need at least 3 '+1' votes from PMC members to allow this release.
> > Currently we have only 2 +1.
> >
> >
> > On 09/04/2017 17:31, Milamber wrote:
> >
> >> Hello,
> >>
> >> The third release candidate for JMeter 3.2 (r1790748) has been prepared,
> >> and your votes are solicited.
> >>
> >> This release brings new features and fixes bugs.
> >>
> >> Please, test this release candidate (with load tests and/or functional
> >> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
> The
> >> feedback are welcome.
> >>
> >> You can read the New and Noteworthy section with some screenshots to
> >> illustrate improvements and full list of changes at:
> >> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
> >>
> >> JMeter is a Java desktop application designed to load test functional
> >> behavior and measure performance. The current version is targeted at
> Java
> >> 8+.
> >>
> >> Download - Archives/hashes/sigs:
> >>
> >> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
> >> (dist revision r19091)
> >>
> >> RAT report:
> >>
> >> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-
> >> report-jmeter-3.2RC3.txt
> >>
> >> MD5 hashes of archives for this vote:
> >>
> >> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
> >> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
> >> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
> >> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
> >>
> >> Site Docs are here:
> >> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
> >>
> >> Maven staging repository is accessible here:
> >> https://repository.apache.org/content/repositories/orgapache
> >> jmeter-1017/org/apache/jmeter/
> >>
> >> Tag:
> >> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
> >>
> >> Keys are here:
> >> https://www.apache.org/dist/jmeter/KEYS
> >>
> >> N.B.
> >> To download the dependencies: "ant download_jars"
> >>
> >> To create the jars and test JMeter: "ant package test".
> >>
> >> JMeter 3.2 requires Java 8 or later to run.
> >>
> >> Some known issues and incompatible changes are listed on changes page.
> >> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.
> >> html#Known%20problems%20and%20workarounds
> >>
> >>
> >> All feedback and vote are welcome.
> >>
> >> [  ] +1  I support this release
> >> [  ] +0  I am OK with this release
> >> [  ] -0   OK, but
> >> [  ] -1   I do not support this release (please indicate why)
> >>
> >> The vote will remain open for at least 72 hours.
> >>
> >> The PMC members please indicate the mention "(binding)" with your vote.
> >>
> >>
> >> Note: If the vote passes, the intention is to release the archive files
> >> and rename the RC tag as the release tag.
> >>
> >> Thanks in advance!
> >>
> >> Milamber
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
>



-- 
Christophe Dumont
Rue du Chapoteyre
38450 Miribel Lanchatre
0633475733

Re: [VOTE] Release JMeter 3.2 RC3

[Maxime Chassagneux]

My vote : +1

2017-04-13 9:46 GMT+02:00 Milamber :

>
> @PMC
>
> We need at least 3 '+1' votes from PMC members to allow this release.
> Currently we have only 2 +1.
>
>
> On 09/04/2017 17:31, Milamber wrote:
>
>> Hello,
>>
>> The third release candidate for JMeter 3.2 (r1790748) has been prepared,
>> and your votes are solicited.
>>
>> This release brings new features and fixes bugs.
>>
>> Please, test this release candidate (with load tests and/or functional
>> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes. The
>> feedback are welcome.
>>
>> You can read the New and Noteworthy section with some screenshots to
>> illustrate improvements and full list of changes at:
>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
>>
>> JMeter is a Java desktop application designed to load test functional
>> behavior and measure performance. The current version is targeted at Java
>> 8+.
>>
>> Download - Archives/hashes/sigs:
>>
>> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
>> (dist revision r19091)
>>
>> RAT report:
>>
>> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-
>> report-jmeter-3.2RC3.txt
>>
>> MD5 hashes of archives for this vote:
>>
>> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
>> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
>> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
>> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
>>
>> Site Docs are here:
>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
>>
>> Maven staging repository is accessible here:
>> https://repository.apache.org/content/repositories/orgapache
>> jmeter-1017/org/apache/jmeter/
>>
>> Tag:
>> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
>>
>> Keys are here:
>> https://www.apache.org/dist/jmeter/KEYS
>>
>> N.B.
>> To download the dependencies: "ant download_jars"
>>
>> To create the jars and test JMeter: "ant package test".
>>
>> JMeter 3.2 requires Java 8 or later to run.
>>
>> Some known issues and incompatible changes are listed on changes page.
>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.
>> html#Known%20problems%20and%20workarounds
>>
>>
>> All feedback and vote are welcome.
>>
>> [  ] +1  I support this release
>> [  ] +0  I am OK with this release
>> [  ] -0   OK, but
>> [  ] -1   I do not support this release (please indicate why)
>>
>> The vote will remain open for at least 72 hours.
>>
>> The PMC members please indicate the mention "(binding)" with your vote.
>>
>>
>> Note: If the vote passes, the intention is to release the archive files
>> and rename the RC tag as the release tag.
>>
>> Thanks in advance!
>>
>> Milamber
>>
>>
>>
>>
>>
>>
>>
>>
>

Re: [VOTE] Release JMeter 3.2 RC3

[Milamber]

@PMC

We need at least 3 '+1' votes from PMC members to allow this release. 
Currently we have only 2 +1.



On 09/04/2017 17:31, Milamber wrote:

Hello,

The third release candidate for JMeter 3.2 (r1790748) has been 
prepared, and your votes are solicited.


This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional 
tests) using Java 8 on Linux/Windows/Mac OS, especially on the 
changes. The feedback are welcome.


You can read the New and Noteworthy section with some screenshots to 
illustrate improvements and full list of changes at:

http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html

JMeter is a Java desktop application designed to load test functional 
behavior and measure performance. The current version is targeted at 
Java 8+.


Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
(dist revision r19091)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt 



MD5 hashes of archives for this vote:

04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/ 



Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds 




All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

Re: [VOTE] Release JMeter 3.2 RC3

[Milamber]

My vote : +1

On 09/04/2017 17:31, Milamber wrote:

Hello,

The third release candidate for JMeter 3.2 (r1790748) has been 
prepared, and your votes are solicited.


This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional 
tests) using Java 8 on Linux/Windows/Mac OS, especially on the 
changes. The feedback are welcome.


You can read the New and Noteworthy section with some screenshots to 
illustrate improvements and full list of changes at:

http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html

JMeter is a Java desktop application designed to load test functional 
behavior and measure performance. The current version is targeted at 
Java 8+.


Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
(dist revision r19091)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt 



MD5 hashes of archives for this vote:

04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/ 



Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds 




All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

Re: [VOTE] Release JMeter 3.2 RC3

[Andrey Pokhilko]

+1

Andrey Pokhilko

On 09.04.2017 19:31, Milamber wrote:
> Hello,
>
> The third release candidate for JMeter 3.2 (r1790748) has been
> prepared, and your votes are solicited.
>
> This release brings new features and fixes bugs.
>
> Please, test this release candidate (with load tests and/or functional
> tests) using Java 8 on Linux/Windows/Mac OS, especially on the
> changes. The feedback are welcome.
>
> You can read the New and Noteworthy section with some screenshots to
> illustrate improvements and full list of changes at:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
>
> JMeter is a Java desktop application designed to load test functional
> behavior and measure performance. The current version is targeted at
> Java 8+.
>
> Download - Archives/hashes/sigs:
>
> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
> (dist revision r19091)
>
> RAT report:
>
> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt
>
>
> MD5 hashes of archives for this vote:
>
> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
>
> Site Docs are here:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
>
> Maven staging repository is accessible here:
> https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/
>
>
> Tag:
> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
>
> Keys are here:
> https://www.apache.org/dist/jmeter/KEYS
>
> N.B.
> To download the dependencies: "ant download_jars"
>
> To create the jars and test JMeter: "ant package test".
>
> JMeter 3.2 requires Java 8 or later to run.
>
> Some known issues and incompatible changes are listed on changes page.
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds
>
>
>
> All feedback and vote are welcome.
> 
> [  ] +1  I support this release
> [  ] +0  I am OK with this release
> [  ] -0   OK, but
> [  ] -1   I do not support this release (please indicate why)
>
> The vote will remain open for at least 72 hours.
>
> The PMC members please indicate the mention "(binding)" with your vote.
>
>
> Note: If the vote passes, the intention is to release the archive files
> and rename the RC tag as the release tag.
>
> Thanks in advance!
>
> Milamber
>
>
>
>
>
>

Re: [VOTE] Release JMeter 3.2 RC3

[Philippe Mouawad]

Thanks to RM!

[+1] I support this release.

Regards

On Sunday, April 9, 2017, Milamber  wrote:

> Hello,
>
> The third release candidate for JMeter 3.2 (r1790748) has been prepared,
> and your votes are solicited.
>
> This release brings new features and fixes bugs.
>
> Please, test this release candidate (with load tests and/or functional
> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes. The
> feedback are welcome.
>
> You can read the New and Noteworthy section with some screenshots to
> illustrate improvements and full list of changes at:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
>
> JMeter is a Java desktop application designed to load test functional
> behavior and measure performance. The current version is targeted at Java
> 8+.
>
> Download - Archives/hashes/sigs:
>
> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
> (dist revision r19091)
>
> RAT report:
>
> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-
> report-jmeter-3.2RC3.txt
>
> MD5 hashes of archives for this vote:
>
> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
>
> Site Docs are here:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
>
> Maven staging repository is accessible here:
> https://repository.apache.org/content/repositories/orgapache
> jmeter-1017/org/apache/jmeter/
>
> Tag:
> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
>
> Keys are here:
> https://www.apache.org/dist/jmeter/KEYS
>
> N.B.
> To download the dependencies: "ant download_jars"
>
> To create the jars and test JMeter: "ant package test".
>
> JMeter 3.2 requires Java 8 or later to run.
>
> Some known issues and incompatible changes are listed on changes page.
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.
> html#Known%20problems%20and%20workarounds
>
>
> All feedback and vote are welcome.
>
> [  ] +1  I support this release
> [  ] +0  I am OK with this release
> [  ] -0   OK, but
> [  ] -1   I do not support this release (please indicate why)
>
> The vote will remain open for at least 72 hours.
>
> The PMC members please indicate the mention "(binding)" with your vote.
>
>
> Note: If the vote passes, the intention is to release the archive files
> and rename the RC tag as the release tag.
>
> Thanks in advance!
>
> Milamber
>
>
>
>
>
>
>

-- 
Cordialement.
Philippe Mouawad.

Re: [VOTE] Release JMeter 3.2 RC3

[Milamber]

On 10/04/2017 13:32, sebb wrote:

I think I have found the Windows issue.
Instead of failing, the test code logs a message if it cannot find the
properties file:

2017-04-10 11:46:32,771 ERROR o.a.j.r.d.ApdexPerTransactionTest:
Problem loading properties. java.io.FileNotFoundException:
F:\jenkins\jenkins-slave\workspace\JMeter%20Windows\trunk\test\resources\org\apache\jmeter\report\dashboard\reportgenerator_test.properties
(The system cannot find the path specified)

I suspect this may be due to the space in the path name.
@Milamber Perhaps you could try that locally?


Ok, I have this issue too if I use a path with a directory name using a 
space.


It was fixed by your commit r1790830 (bug 60966). Thanks Sebb.




I know we recommend not to use spaces, but we should try and fix such
issues when they become apparent.

The test should fail if the file cannot be found.
[I wonder how many other test cases use the same strategy.]


On 10 April 2017 at 13:04, sebb  wrote:

There are also frequent failures with the Ubuntu builds in the test:

TestSchedulerWithTimer

This is possibly a timing issue, but again I don't think it's a good
idea to ignore such errors.

I have added an extra test to try and debug the Windows failure - it
looks like the Props collection is empty.

On 10 April 2017 at 11:14, sebb  wrote:

On 10 April 2017 at 08:07, Milamber  wrote:

On my Windows 10 virtual machine, I built successfully JMeter from svn
trunk. I don't why we have this issue... The Jenkins machine is a Windows
2012 R2, perhaps they have some differences with Windows 10 for this test?

Possibly.
But JMeter users may have the same problem, so the failure cannot just
be ignored.

We need to know what the cause is.
It may perhaps be specific to the Jenkins build, but that seems unlikely.


On 10/04/2017 01:58, sebb wrote:

The last few Windows builds have failed with


testgetApdexPerTransactionProperty(org.apache.jmeter.report.dashboard.ApdexPerTransactionTest)
   [java] java.lang.AssertionError:
expected:
but was:


Has anyone investigated that?

On 9 April 2017 at 17:31, Milamber  wrote:

Hello,

The third release candidate for JMeter 3.2 (r1790748) has been prepared,
and
your votes are solicited.

This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional
tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
The
feedback are welcome.

You can read the New and Noteworthy section with some screenshots to
illustrate improvements and full list of changes at:
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html

JMeter is a Java desktop application designed to load test functional
behavior and measure performance. The current version is targeted at Java
8+.

Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
(dist revision r19091)

RAT report:


http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt

MD5 hashes of archives for this vote:

04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/

Maven staging repository is accessible here:

https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/

Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.

http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds


All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

Re: [VOTE] Release JMeter 3.2 RC3

[sebb]

I think I have found the Windows issue.
Instead of failing, the test code logs a message if it cannot find the
properties file:

2017-04-10 11:46:32,771 ERROR o.a.j.r.d.ApdexPerTransactionTest:
Problem loading properties. java.io.FileNotFoundException:
F:\jenkins\jenkins-slave\workspace\JMeter%20Windows\trunk\test\resources\org\apache\jmeter\report\dashboard\reportgenerator_test.properties
(The system cannot find the path specified)

I suspect this may be due to the space in the path name.
@Milamber Perhaps you could try that locally?

I know we recommend not to use spaces, but we should try and fix such
issues when they become apparent.

The test should fail if the file cannot be found.
[I wonder how many other test cases use the same strategy.]


On 10 April 2017 at 13:04, sebb  wrote:
> There are also frequent failures with the Ubuntu builds in the test:
>
> TestSchedulerWithTimer
>
> This is possibly a timing issue, but again I don't think it's a good
> idea to ignore such errors.
>
> I have added an extra test to try and debug the Windows failure - it
> looks like the Props collection is empty.
>
> On 10 April 2017 at 11:14, sebb  wrote:
>> On 10 April 2017 at 08:07, Milamber  wrote:
>>>
>>> On my Windows 10 virtual machine, I built successfully JMeter from svn
>>> trunk. I don't why we have this issue... The Jenkins machine is a Windows
>>> 2012 R2, perhaps they have some differences with Windows 10 for this test?
>>
>> Possibly.
>> But JMeter users may have the same problem, so the failure cannot just
>> be ignored.
>>
>> We need to know what the cause is.
>> It may perhaps be specific to the Jenkins build, but that seems unlikely.
>>
>>>
>>> On 10/04/2017 01:58, sebb wrote:

 The last few Windows builds have failed with


 testgetApdexPerTransactionProperty(org.apache.jmeter.report.dashboard.ApdexPerTransactionTest)
   [java] java.lang.AssertionError:
 expected:
 but was:


 Has anyone investigated that?

 On 9 April 2017 at 17:31, Milamber  wrote:
>
> Hello,
>
> The third release candidate for JMeter 3.2 (r1790748) has been prepared,
> and
> your votes are solicited.
>
> This release brings new features and fixes bugs.
>
> Please, test this release candidate (with load tests and/or functional
> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
> The
> feedback are welcome.
>
> You can read the New and Noteworthy section with some screenshots to
> illustrate improvements and full list of changes at:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
>
> JMeter is a Java desktop application designed to load test functional
> behavior and measure performance. The current version is targeted at Java
> 8+.
>
> Download - Archives/hashes/sigs:
>
> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
> (dist revision r19091)
>
> RAT report:
>
>
> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt
>
> MD5 hashes of archives for this vote:
>
> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
>
> Site Docs are here:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
>
> Maven staging repository is accessible here:
>
> https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/
>
> Tag:
> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
>
> Keys are here:
> https://www.apache.org/dist/jmeter/KEYS
>
> N.B.
> To download the dependencies: "ant download_jars"
>
> To create the jars and test JMeter: "ant package test".
>
> JMeter 3.2 requires Java 8 or later to run.
>
> Some known issues and incompatible changes are listed on changes page.
>
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds
>
>
> All feedback and vote are welcome.
>
> [  ] +1  I support this release
> [  ] +0  I am OK with this release
> [  ] -0   OK, but
> [  ] -1   I do not support this release (please indicate why)
>
> The vote will remain open for at least 72 hours.
>
> The PMC members please indicate the mention "(binding)" with your vote.
>
>
> Note: If the vote passes, the intention is to release the archive files
> and rename the RC tag as the release tag.
>
> Thanks in advance!
>
> Milamber
>
>
>
>
>
>
>>>

Re: [VOTE] Release JMeter 3.2 RC3

[sebb]

There are also frequent failures with the Ubuntu builds in the test:

TestSchedulerWithTimer

This is possibly a timing issue, but again I don't think it's a good
idea to ignore such errors.

I have added an extra test to try and debug the Windows failure - it
looks like the Props collection is empty.

On 10 April 2017 at 11:14, sebb  wrote:
> On 10 April 2017 at 08:07, Milamber  wrote:
>>
>> On my Windows 10 virtual machine, I built successfully JMeter from svn
>> trunk. I don't why we have this issue... The Jenkins machine is a Windows
>> 2012 R2, perhaps they have some differences with Windows 10 for this test?
>
> Possibly.
> But JMeter users may have the same problem, so the failure cannot just
> be ignored.
>
> We need to know what the cause is.
> It may perhaps be specific to the Jenkins build, but that seems unlikely.
>
>>
>> On 10/04/2017 01:58, sebb wrote:
>>>
>>> The last few Windows builds have failed with
>>>
>>>
>>> testgetApdexPerTransactionProperty(org.apache.jmeter.report.dashboard.ApdexPerTransactionTest)
>>>   [java] java.lang.AssertionError:
>>> expected:
>>> but was:
>>>
>>>
>>> Has anyone investigated that?
>>>
>>> On 9 April 2017 at 17:31, Milamber  wrote:

 Hello,

 The third release candidate for JMeter 3.2 (r1790748) has been prepared,
 and
 your votes are solicited.

 This release brings new features and fixes bugs.

 Please, test this release candidate (with load tests and/or functional
 tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
 The
 feedback are welcome.

 You can read the New and Noteworthy section with some screenshots to
 illustrate improvements and full list of changes at:
 http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html

 JMeter is a Java desktop application designed to load test functional
 behavior and measure performance. The current version is targeted at Java
 8+.

 Download - Archives/hashes/sigs:

 https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
 (dist revision r19091)

 RAT report:


 http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt

 MD5 hashes of archives for this vote:

 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
 a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
 d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip

 Site Docs are here:
 http://home.apache.org/~milamber/jmeter-3.2RC3/docs/

 Maven staging repository is accessible here:

 https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/

 Tag:
 https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/

 Keys are here:
 https://www.apache.org/dist/jmeter/KEYS

 N.B.
 To download the dependencies: "ant download_jars"

 To create the jars and test JMeter: "ant package test".

 JMeter 3.2 requires Java 8 or later to run.

 Some known issues and incompatible changes are listed on changes page.

 http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds


 All feedback and vote are welcome.

 [  ] +1  I support this release
 [  ] +0  I am OK with this release
 [  ] -0   OK, but
 [  ] -1   I do not support this release (please indicate why)

 The vote will remain open for at least 72 hours.

 The PMC members please indicate the mention "(binding)" with your vote.


 Note: If the vote passes, the intention is to release the archive files
 and rename the RC tag as the release tag.

 Thanks in advance!

 Milamber






>>

Re: [VOTE] Release JMeter 3.2 RC3

[sebb]

On 10 April 2017 at 08:07, Milamber  wrote:
>
> On my Windows 10 virtual machine, I built successfully JMeter from svn
> trunk. I don't why we have this issue... The Jenkins machine is a Windows
> 2012 R2, perhaps they have some differences with Windows 10 for this test?

Possibly.
But JMeter users may have the same problem, so the failure cannot just
be ignored.

We need to know what the cause is.
It may perhaps be specific to the Jenkins build, but that seems unlikely.

>
> On 10/04/2017 01:58, sebb wrote:
>>
>> The last few Windows builds have failed with
>>
>>
>> testgetApdexPerTransactionProperty(org.apache.jmeter.report.dashboard.ApdexPerTransactionTest)
>>   [java] java.lang.AssertionError:
>> expected:
>> but was:
>>
>>
>> Has anyone investigated that?
>>
>> On 9 April 2017 at 17:31, Milamber  wrote:
>>>
>>> Hello,
>>>
>>> The third release candidate for JMeter 3.2 (r1790748) has been prepared,
>>> and
>>> your votes are solicited.
>>>
>>> This release brings new features and fixes bugs.
>>>
>>> Please, test this release candidate (with load tests and/or functional
>>> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
>>> The
>>> feedback are welcome.
>>>
>>> You can read the New and Noteworthy section with some screenshots to
>>> illustrate improvements and full list of changes at:
>>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
>>>
>>> JMeter is a Java desktop application designed to load test functional
>>> behavior and measure performance. The current version is targeted at Java
>>> 8+.
>>>
>>> Download - Archives/hashes/sigs:
>>>
>>> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
>>> (dist revision r19091)
>>>
>>> RAT report:
>>>
>>>
>>> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt
>>>
>>> MD5 hashes of archives for this vote:
>>>
>>> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
>>> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
>>> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
>>> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
>>>
>>> Site Docs are here:
>>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
>>>
>>> Maven staging repository is accessible here:
>>>
>>> https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/
>>>
>>> Tag:
>>> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
>>>
>>> Keys are here:
>>> https://www.apache.org/dist/jmeter/KEYS
>>>
>>> N.B.
>>> To download the dependencies: "ant download_jars"
>>>
>>> To create the jars and test JMeter: "ant package test".
>>>
>>> JMeter 3.2 requires Java 8 or later to run.
>>>
>>> Some known issues and incompatible changes are listed on changes page.
>>>
>>> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds
>>>
>>>
>>> All feedback and vote are welcome.
>>>
>>> [  ] +1  I support this release
>>> [  ] +0  I am OK with this release
>>> [  ] -0   OK, but
>>> [  ] -1   I do not support this release (please indicate why)
>>>
>>> The vote will remain open for at least 72 hours.
>>>
>>> The PMC members please indicate the mention "(binding)" with your vote.
>>>
>>>
>>> Note: If the vote passes, the intention is to release the archive files
>>> and rename the RC tag as the release tag.
>>>
>>> Thanks in advance!
>>>
>>> Milamber
>>>
>>>
>>>
>>>
>>>
>>>
>

Re: [VOTE] Release JMeter 3.2 RC3

[Milamber]

On my Windows 10 virtual machine, I built successfully JMeter from svn 
trunk. I don't why we have this issue... The Jenkins machine is a 
Windows 2012 R2, perhaps they have some differences with Windows 10 for 
this test?


On 10/04/2017 01:58, sebb wrote:

The last few Windows builds have failed with

testgetApdexPerTransactionProperty(org.apache.jmeter.report.dashboard.ApdexPerTransactionTest)
  [java] java.lang.AssertionError:
expected:
but was:


Has anyone investigated that?

On 9 April 2017 at 17:31, Milamber  wrote:

Hello,

The third release candidate for JMeter 3.2 (r1790748) has been prepared, and
your votes are solicited.

This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional
tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes. The
feedback are welcome.

You can read the New and Noteworthy section with some screenshots to
illustrate improvements and full list of changes at:
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html

JMeter is a Java desktop application designed to load test functional
behavior and measure performance. The current version is targeted at Java
8+.

Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
(dist revision r19091)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt

MD5 hashes of archives for this vote:

04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/

Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds


All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

Re: [VOTE] Release JMeter 3.2 RC3

[sebb]

The last few Windows builds have failed with

testgetApdexPerTransactionProperty(org.apache.jmeter.report.dashboard.ApdexPerTransactionTest)
 [java] java.lang.AssertionError:
expected:
but was:


Has anyone investigated that?

On 9 April 2017 at 17:31, Milamber  wrote:
> Hello,
>
> The third release candidate for JMeter 3.2 (r1790748) has been prepared, and
> your votes are solicited.
>
> This release brings new features and fixes bugs.
>
> Please, test this release candidate (with load tests and/or functional
> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes. The
> feedback are welcome.
>
> You can read the New and Noteworthy section with some screenshots to
> illustrate improvements and full list of changes at:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html
>
> JMeter is a Java desktop application designed to load test functional
> behavior and measure performance. The current version is targeted at Java
> 8+.
>
> Download - Archives/hashes/sigs:
>
> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
> (dist revision r19091)
>
> RAT report:
>
> http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt
>
> MD5 hashes of archives for this vote:
>
> 04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
> a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
> 28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
> d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip
>
> Site Docs are here:
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/
>
> Maven staging repository is accessible here:
> https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/
>
> Tag:
> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/
>
> Keys are here:
> https://www.apache.org/dist/jmeter/KEYS
>
> N.B.
> To download the dependencies: "ant download_jars"
>
> To create the jars and test JMeter: "ant package test".
>
> JMeter 3.2 requires Java 8 or later to run.
>
> Some known issues and incompatible changes are listed on changes page.
> http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds
>
>
> All feedback and vote are welcome.
>
> [  ] +1  I support this release
> [  ] +0  I am OK with this release
> [  ] -0   OK, but
> [  ] -1   I do not support this release (please indicate why)
>
> The vote will remain open for at least 72 hours.
>
> The PMC members please indicate the mention "(binding)" with your vote.
>
>
> Note: If the vote passes, the intention is to release the archive files
> and rename the RC tag as the release tag.
>
> Thanks in advance!
>
> Milamber
>
>
>
>
>
>

[VOTE] Release JMeter 3.2 RC3

[Milamber]

Hello,

The third release candidate for JMeter 3.2 (r1790748) has been prepared, 
and your votes are solicited.


This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional 
tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes. 
The feedback are welcome.


You can read the New and Noteworthy section with some screenshots to 
illustrate improvements and full list of changes at:

http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html

JMeter is a Java desktop application designed to load test functional 
behavior and measure performance. The current version is targeted at 
Java 8+.


Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC3/
(dist revision r19091)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC3/dist/rat-report-jmeter-3.2RC3.txt

MD5 hashes of archives for this vote:

04a0119f3c66ec157d78725135f79863 *apache-jmeter-3.2.tgz
a670f1160621710d69136851d26c5b56 *apache-jmeter-3.2.zip
28b99b6155f2ae5ac7d9440915f1e3a0 *apache-jmeter-3.2_src.tgz
d5936f4f471b6b84c0d7f8b5c75ea72d *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1017/org/apache/jmeter/

Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC3/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC3/docs/changes.html#Known%20problems%20and%20workarounds


All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

[CANCELLED] Re: [VOTE] Release JMeter 3.2 RC2

[Milamber]

Hello,

Due of the API backward issue with Ubik plugin, I cancel the vote and 
start the next RC3 asap.


Milamber

On 01/04/2017 16:23, Milamber wrote:

Hello,

The second release candidate for JMeter 3.2 (r1789808) has been 
prepared, and your votes are solicited.


This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional 
tests) using Java 8 on Linux/Windows/Mac OS, especially on the 
changes. The feedback are welcome.


You can read the New and Noteworthy section with some screenshots to 
illustrate improvements and full list of changes at:

http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html

JMeter is a Java desktop application designed to load test functional 
behavior and measure performance. The current version is targeted at 
Java 8+.


Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
(dist revision r18998)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-report-jmeter-3.2RC2.txt 



MD5 hashes of archives for this vote:

cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1016/org/apache/jmeter/ 



Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html#Known%20problems%20and%20workarounds 




All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

Re: [VOTE] Release JMeter 3.2 RC2

[sebb]

On 4 April 2017 at 10:49, sebb <seb...@gmail.com> wrote:
> On 4 April 2017 at 09:52, sebb <seb...@gmail.com> wrote:
>> On 3 April 2017 at 21:52, Philippe Mouawad <philippe.moua...@gmail.com> 
>> wrote:
>>> Thanks Milamber !
>>> Maybe we should run this tool (
>>> https://github.com/lvc/japi-compliance-checker) on JMeter 3.2 RC2 vs 3.1 to
>>> double check there are no other similar non identified issues.
>>
>> That would have to be done individually by each developer.
>> The license is not suitable for inclusion in JMeter itself.
>> Also it relies on Perl, which would have to be installed separately.
>>
>
> Commons use Clirr or Japicmp
>
> From what I have seen of Japicmp, the reports are extremely verbose
> but don't make the incompatibililies nearly obvious enough.
> But that might be a problem with the Maven wrapper or its config.

Also Japicmp appears to ignore changes to constant values.
Clirr at least reports this as a warning.

>>> Regards
>>>
>>> On Mon, Apr 3, 2017 at 9:20 PM, Milamber <milam...@apache.org> wrote:
>>>
>>>> Hello,
>>>>
>>>> I will cancel the RC2 vote and start a RC3 next Wednesday or Friday (after
>>>> the re-introduction of the removed API. cc Philippe).
>>>>
>>>> Please continue your test about RC2 to find a lot of bugs before the RC3
>>>> ;-)
>>>>
>>>> Milamber
>>>>
>>>>
>>>> On 03/04/2017 10:45, Antonio Gomes Rodrigues wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Like Philippe
>>>>>
>>>>> [X] I do not support this release
>>>>>
>>>>> In my opinion, we need to deprecate this API in 3.2 release and remove it
>>>>> in 3.3
>>>>>
>>>>> Antonio
>>>>>
>>>>> 2017-04-03 7:40 GMT+02:00 Philippe Mouawad <p.moua...@ubik-ingenierie.com
>>>>> >:
>>>>>
>>>>> Hello,
>>>>>> Thanks Milamber for your work on RM for this.
>>>>>>
>>>>>> Due to issue reported my vote is:
>>>>>>
>>>>>> [X] I do not support this release
>>>>>>
>>>>>> I can fix issue if ok for you to commit in trunk.
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> On Sunday, April 2, 2017, Philippe Mouawad <
>>>>>> p.moua...@ubik-ingenierie.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>> I am to blame for this issue, sorry !
>>>>>>> http://svn.apache.org/viewvc?rev=1783666=rev
>>>>>>>
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
>>>>>>> supp...@ubikloadpack.com
>>>>>>> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>> Note this is annoying as fixing it would mean that our plugin would
>>>>>>>> only
>>>>>>>> support 3.2.
>>>>>>>> We usually try to support N and N-1 versions to allow for migration.
>>>>>>>> And this was usually the policy with JMeter releases.
>>>>>>>>
>>>>>>>> Hope you can take this into account.
>>>>>>>> Regards
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
>>>>>>>> supp...@ubikloadpack.com
>>>>>>>> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>> First thanks a lot for all the team for the great work on Apache
>>>>>>>>> JMeter
>>>>>>>>> and thanks to RM !
>>>>>>>>>
>>>>>>>>> Now for this release, it appears HeaderManager API has been modified
>>>>>>>>> in
>>>>>>>>> a breaking and undocumented way:
>>>>>>>>> This method:
&

Re: [VOTE] Release JMeter 3.2 RC2

[sebb]

On 4 April 2017 at 09:52, sebb <seb...@gmail.com> wrote:
> On 3 April 2017 at 21:52, Philippe Mouawad <philippe.moua...@gmail.com> wrote:
>> Thanks Milamber !
>> Maybe we should run this tool (
>> https://github.com/lvc/japi-compliance-checker) on JMeter 3.2 RC2 vs 3.1 to
>> double check there are no other similar non identified issues.
>
> That would have to be done individually by each developer.
> The license is not suitable for inclusion in JMeter itself.
> Also it relies on Perl, which would have to be installed separately.
>

Commons use Clirr or Japicmp

>From what I have seen of Japicmp, the reports are extremely verbose
but don't make the incompatibililies nearly obvious enough.
But that might be a problem with the Maven wrapper or its config.

>> Regards
>>
>> On Mon, Apr 3, 2017 at 9:20 PM, Milamber <milam...@apache.org> wrote:
>>
>>> Hello,
>>>
>>> I will cancel the RC2 vote and start a RC3 next Wednesday or Friday (after
>>> the re-introduction of the removed API. cc Philippe).
>>>
>>> Please continue your test about RC2 to find a lot of bugs before the RC3
>>> ;-)
>>>
>>> Milamber
>>>
>>>
>>> On 03/04/2017 10:45, Antonio Gomes Rodrigues wrote:
>>>
>>>> Hi,
>>>>
>>>> Like Philippe
>>>>
>>>> [X] I do not support this release
>>>>
>>>> In my opinion, we need to deprecate this API in 3.2 release and remove it
>>>> in 3.3
>>>>
>>>> Antonio
>>>>
>>>> 2017-04-03 7:40 GMT+02:00 Philippe Mouawad <p.moua...@ubik-ingenierie.com
>>>> >:
>>>>
>>>> Hello,
>>>>> Thanks Milamber for your work on RM for this.
>>>>>
>>>>> Due to issue reported my vote is:
>>>>>
>>>>> [X] I do not support this release
>>>>>
>>>>> I can fix issue if ok for you to commit in trunk.
>>>>>
>>>>> Regards
>>>>>
>>>>> On Sunday, April 2, 2017, Philippe Mouawad <
>>>>> p.moua...@ubik-ingenierie.com>
>>>>> wrote:
>>>>>
>>>>> Hello,
>>>>>> I am to blame for this issue, sorry !
>>>>>> http://svn.apache.org/viewvc?rev=1783666=rev
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>>
>>>>>> On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
>>>>>> supp...@ubikloadpack.com
>>>>>> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>> Note this is annoying as fixing it would mean that our plugin would
>>>>>>> only
>>>>>>> support 3.2.
>>>>>>> We usually try to support N and N-1 versions to allow for migration.
>>>>>>> And this was usually the policy with JMeter releases.
>>>>>>>
>>>>>>> Hope you can take this into account.
>>>>>>> Regards
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
>>>>>>> supp...@ubikloadpack.com
>>>>>>> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>> First thanks a lot for all the team for the great work on Apache
>>>>>>>> JMeter
>>>>>>>> and thanks to RM !
>>>>>>>>
>>>>>>>> Now for this release, it appears HeaderManager API has been modified
>>>>>>>> in
>>>>>>>> a breaking and undocumented way:
>>>>>>>> This method:
>>>>>>>>
>>>>>>>> - https://github.com/apache/jmeter/blob/v3_1/src/protocol/http
>>>>>>>> /org/apache/jmeter/protocol/http/control/HeaderManager.java#L268
>>>>>>>> <https://github.com/apache/jmeter/blob/v3_1/src/protocol/
>>>>>>>>
>>>>>>> http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268>
>>>>>
>>>>>> Has been modified:
>>>>>>>>
>>>>>>>&g

Re: [VOTE] Release JMeter 3.2 RC2

[sebb]

On 3 April 2017 at 21:52, Philippe Mouawad <philippe.moua...@gmail.com> wrote:
> Thanks Milamber !
> Maybe we should run this tool (
> https://github.com/lvc/japi-compliance-checker) on JMeter 3.2 RC2 vs 3.1 to
> double check there are no other similar non identified issues.

That would have to be done individually by each developer.
The license is not suitable for inclusion in JMeter itself.
Also it relies on Perl, which would have to be installed separately.


> Regards
>
> On Mon, Apr 3, 2017 at 9:20 PM, Milamber <milam...@apache.org> wrote:
>
>> Hello,
>>
>> I will cancel the RC2 vote and start a RC3 next Wednesday or Friday (after
>> the re-introduction of the removed API. cc Philippe).
>>
>> Please continue your test about RC2 to find a lot of bugs before the RC3
>> ;-)
>>
>> Milamber
>>
>>
>> On 03/04/2017 10:45, Antonio Gomes Rodrigues wrote:
>>
>>> Hi,
>>>
>>> Like Philippe
>>>
>>> [X] I do not support this release
>>>
>>> In my opinion, we need to deprecate this API in 3.2 release and remove it
>>> in 3.3
>>>
>>> Antonio
>>>
>>> 2017-04-03 7:40 GMT+02:00 Philippe Mouawad <p.moua...@ubik-ingenierie.com
>>> >:
>>>
>>> Hello,
>>>> Thanks Milamber for your work on RM for this.
>>>>
>>>> Due to issue reported my vote is:
>>>>
>>>> [X] I do not support this release
>>>>
>>>> I can fix issue if ok for you to commit in trunk.
>>>>
>>>> Regards
>>>>
>>>> On Sunday, April 2, 2017, Philippe Mouawad <
>>>> p.moua...@ubik-ingenierie.com>
>>>> wrote:
>>>>
>>>> Hello,
>>>>> I am to blame for this issue, sorry !
>>>>> http://svn.apache.org/viewvc?rev=1783666=rev
>>>>>
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>> On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
>>>>> supp...@ubikloadpack.com
>>>>> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
>>>>>
>>>>> Hello,
>>>>>> Note this is annoying as fixing it would mean that our plugin would
>>>>>> only
>>>>>> support 3.2.
>>>>>> We usually try to support N and N-1 versions to allow for migration.
>>>>>> And this was usually the policy with JMeter releases.
>>>>>>
>>>>>> Hope you can take this into account.
>>>>>> Regards
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
>>>>>> supp...@ubikloadpack.com
>>>>>> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>> First thanks a lot for all the team for the great work on Apache
>>>>>>> JMeter
>>>>>>> and thanks to RM !
>>>>>>>
>>>>>>> Now for this release, it appears HeaderManager API has been modified
>>>>>>> in
>>>>>>> a breaking and undocumented way:
>>>>>>> This method:
>>>>>>>
>>>>>>> - https://github.com/apache/jmeter/blob/v3_1/src/protocol/http
>>>>>>> /org/apache/jmeter/protocol/http/control/HeaderManager.java#L268
>>>>>>> <https://github.com/apache/jmeter/blob/v3_1/src/protocol/
>>>>>>>
>>>>>> http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268>
>>>>
>>>>> Has been modified:
>>>>>>>
>>>>>>> - https://github.com/apache/jmeter/blob/v3_2_RC2/src/protocol/
>>>>>>> http/org/apache/jmeter/protocol/http/control/
>>>>>>>
>>>>>> HeaderManager.java#L234
>>>>
>>>>> <https://github.com/apache/jmeter/blob/v3_2_RC2/src/
>>>>>>>
>>>>>> protocol/http/org/apache/jmeter/protocol/http/control/
>>>> HeaderManager.java#L234>
>>>>
>>>>>
>>>>>>> This would unfortunately break our plugin.
>>>>>>>
>>>>>>> Is is possible to reintroduce this method and make it deprecate

Re: [VOTE] Release JMeter 3.2 RC2

[Philippe Mouawad]

Thanks Milamber !
Maybe we should run this tool (
https://github.com/lvc/japi-compliance-checker) on JMeter 3.2 RC2 vs 3.1 to
double check there are no other similar non identified issues.

Regards

On Mon, Apr 3, 2017 at 9:20 PM, Milamber <milam...@apache.org> wrote:

> Hello,
>
> I will cancel the RC2 vote and start a RC3 next Wednesday or Friday (after
> the re-introduction of the removed API. cc Philippe).
>
> Please continue your test about RC2 to find a lot of bugs before the RC3
> ;-)
>
> Milamber
>
>
> On 03/04/2017 10:45, Antonio Gomes Rodrigues wrote:
>
>> Hi,
>>
>> Like Philippe
>>
>> [X] I do not support this release
>>
>> In my opinion, we need to deprecate this API in 3.2 release and remove it
>> in 3.3
>>
>> Antonio
>>
>> 2017-04-03 7:40 GMT+02:00 Philippe Mouawad <p.moua...@ubik-ingenierie.com
>> >:
>>
>> Hello,
>>> Thanks Milamber for your work on RM for this.
>>>
>>> Due to issue reported my vote is:
>>>
>>> [X] I do not support this release
>>>
>>> I can fix issue if ok for you to commit in trunk.
>>>
>>> Regards
>>>
>>> On Sunday, April 2, 2017, Philippe Mouawad <
>>> p.moua...@ubik-ingenierie.com>
>>> wrote:
>>>
>>> Hello,
>>>> I am to blame for this issue, sorry !
>>>> http://svn.apache.org/viewvc?rev=1783666=rev
>>>>
>>>>
>>>> Regards
>>>>
>>>>
>>>> On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
>>>> supp...@ubikloadpack.com
>>>> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
>>>>
>>>> Hello,
>>>>> Note this is annoying as fixing it would mean that our plugin would
>>>>> only
>>>>> support 3.2.
>>>>> We usually try to support N and N-1 versions to allow for migration.
>>>>> And this was usually the policy with JMeter releases.
>>>>>
>>>>> Hope you can take this into account.
>>>>> Regards
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
>>>>> supp...@ubikloadpack.com
>>>>> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
>>>>>
>>>>> Hello,
>>>>>> First thanks a lot for all the team for the great work on Apache
>>>>>> JMeter
>>>>>> and thanks to RM !
>>>>>>
>>>>>> Now for this release, it appears HeaderManager API has been modified
>>>>>> in
>>>>>> a breaking and undocumented way:
>>>>>> This method:
>>>>>>
>>>>>> - https://github.com/apache/jmeter/blob/v3_1/src/protocol/http
>>>>>> /org/apache/jmeter/protocol/http/control/HeaderManager.java#L268
>>>>>> <https://github.com/apache/jmeter/blob/v3_1/src/protocol/
>>>>>>
>>>>> http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268>
>>>
>>>> Has been modified:
>>>>>>
>>>>>> - https://github.com/apache/jmeter/blob/v3_2_RC2/src/protocol/
>>>>>> http/org/apache/jmeter/protocol/http/control/
>>>>>>
>>>>> HeaderManager.java#L234
>>>
>>>> <https://github.com/apache/jmeter/blob/v3_2_RC2/src/
>>>>>>
>>>>> protocol/http/org/apache/jmeter/protocol/http/control/
>>> HeaderManager.java#L234>
>>>
>>>>
>>>>>> This would unfortunately break our plugin.
>>>>>>
>>>>>> Is is possible to reintroduce this method and make it deprecated ?
>>>>>>
>>>>>> Thanks
>>>>>> Regards
>>>>>>
>>>>>> UbikLoadPack Team
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Apr 2, 2017 at 12:45 PM, Rainer Jung <rainer.j...@kippdata.de
>>>>>> <javascript:_e(%7B%7D,'cvml','rainer.j...@kippdata.de');>> wrote:
>>>>>>
>>>>>> Am 01.04.2017 um 18:23 schrieb Milamber:
>>>>>>>
>>>>>>> Hello,
>>>>>>>>
>>>>>>>> The second release candidate for JMeter 3.2 (r1789808) has been
&g

Re: [VOTE] Release JMeter 3.2 RC2

[Milamber]

Hello,

I will cancel the RC2 vote and start a RC3 next Wednesday or Friday 
(after the re-introduction of the removed API. cc Philippe).


Please continue your test about RC2 to find a lot of bugs before the RC3 ;-)

Milamber

On 03/04/2017 10:45, Antonio Gomes Rodrigues wrote:

Hi,

Like Philippe

[X] I do not support this release

In my opinion, we need to deprecate this API in 3.2 release and remove it
in 3.3

Antonio

2017-04-03 7:40 GMT+02:00 Philippe Mouawad <p.moua...@ubik-ingenierie.com>:


Hello,
Thanks Milamber for your work on RM for this.

Due to issue reported my vote is:

[X] I do not support this release

I can fix issue if ok for you to commit in trunk.

Regards

On Sunday, April 2, 2017, Philippe Mouawad <p.moua...@ubik-ingenierie.com>
wrote:


Hello,
I am to blame for this issue, sorry !
http://svn.apache.org/viewvc?rev=1783666=rev


Regards


On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
supp...@ubikloadpack.com
<javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:


Hello,
Note this is annoying as fixing it would mean that our plugin would only
support 3.2.
We usually try to support N and N-1 versions to allow for migration.
And this was usually the policy with JMeter releases.

Hope you can take this into account.
Regards




On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
supp...@ubikloadpack.com
<javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:


Hello,
First thanks a lot for all the team for the great work on Apache JMeter
and thanks to RM !

Now for this release, it appears HeaderManager API has been modified in
a breaking and undocumented way:
This method:

- https://github.com/apache/jmeter/blob/v3_1/src/protocol/http
/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268
<https://github.com/apache/jmeter/blob/v3_1/src/protocol/

http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268>

Has been modified:

- https://github.com/apache/jmeter/blob/v3_2_RC2/src/protocol/
http/org/apache/jmeter/protocol/http/control/

HeaderManager.java#L234

<https://github.com/apache/jmeter/blob/v3_2_RC2/src/

protocol/http/org/apache/jmeter/protocol/http/control/
HeaderManager.java#L234>


This would unfortunately break our plugin.

Is is possible to reintroduce this method and make it deprecated ?

Thanks
Regards

UbikLoadPack Team



On Sun, Apr 2, 2017 at 12:45 PM, Rainer Jung <rainer.j...@kippdata.de
<javascript:_e(%7B%7D,'cvml','rainer.j...@kippdata.de');>> wrote:


Am 01.04.2017 um 18:23 schrieb Milamber:


Hello,

The second release candidate for JMeter 3.2 (r1789808) has been
prepared, and your votes are solicited.

This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or

functional

tests) using Java 8 on Linux/Windows/Mac OS, especially on the

changes.

The feedback are welcome.

You can read the New and Noteworthy section with some screenshots to
illustrate improvements and full list of changes at:
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html

JMeter is a Java desktop application designed to load test functional
behavior and measure performance. The current version is targeted at
Java 8+.

Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
(dist revision r18998)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-repo
rt-jmeter-3.2RC2.txt


MD5 hashes of archives for this vote:

cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapache
jmeter-1016/org/apache/jmeter/


Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes

page.

http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.
html#Known%20problems%20and%20workarounds



All feedback and vote are welcome.

[XX] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your

vote.


Note: If the vote passes, the intention is to release the archive

files

and rename the RC tag as the release tag.

Thanks in advance!


+1 (binding), thanks for RM.

Details:

- MD5 OK
- signatur

Re: [VOTE] Release JMeter 3.2 RC2

[Antonio Gomes Rodrigues]

Hi,

Like Philippe

[X] I do not support this release

In my opinion, we need to deprecate this API in 3.2 release and remove it
in 3.3

Antonio

2017-04-03 7:40 GMT+02:00 Philippe Mouawad <p.moua...@ubik-ingenierie.com>:

> Hello,
> Thanks Milamber for your work on RM for this.
>
> Due to issue reported my vote is:
>
> [X] I do not support this release
>
> I can fix issue if ok for you to commit in trunk.
>
> Regards
>
> On Sunday, April 2, 2017, Philippe Mouawad <p.moua...@ubik-ingenierie.com>
> wrote:
>
> > Hello,
> > I am to blame for this issue, sorry !
> > http://svn.apache.org/viewvc?rev=1783666=rev
> >
> >
> > Regards
> >
> >
> > On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
> > supp...@ubikloadpack.com
> > <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
> >
> >> Hello,
> >> Note this is annoying as fixing it would mean that our plugin would only
> >> support 3.2.
> >> We usually try to support N and N-1 versions to allow for migration.
> >> And this was usually the policy with JMeter releases.
> >>
> >> Hope you can take this into account.
> >> Regards
> >>
> >>
> >>
> >>
> >> On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
> >> supp...@ubikloadpack.com
> >> <javascript:_e(%7B%7D,'cvml','supp...@ubikloadpack.com');>> wrote:
> >>
> >>> Hello,
> >>> First thanks a lot for all the team for the great work on Apache JMeter
> >>> and thanks to RM !
> >>>
> >>> Now for this release, it appears HeaderManager API has been modified in
> >>> a breaking and undocumented way:
> >>> This method:
> >>>
> >>>- https://github.com/apache/jmeter/blob/v3_1/src/protocol/http
> >>>/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268
> >>><https://github.com/apache/jmeter/blob/v3_1/src/protocol/
> http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268>
> >>>
> >>> Has been modified:
> >>>
> >>>- https://github.com/apache/jmeter/blob/v3_2_RC2/src/protocol/
> >>>http/org/apache/jmeter/protocol/http/control/
> HeaderManager.java#L234
> >>><https://github.com/apache/jmeter/blob/v3_2_RC2/src/
> protocol/http/org/apache/jmeter/protocol/http/control/
> HeaderManager.java#L234>
> >>>
> >>>
> >>> This would unfortunately break our plugin.
> >>>
> >>> Is is possible to reintroduce this method and make it deprecated ?
> >>>
> >>> Thanks
> >>> Regards
> >>>
> >>> UbikLoadPack Team
> >>>
> >>>
> >>>
> >>> On Sun, Apr 2, 2017 at 12:45 PM, Rainer Jung <rainer.j...@kippdata.de
> >>> <javascript:_e(%7B%7D,'cvml','rainer.j...@kippdata.de');>> wrote:
> >>>
> >>>> Am 01.04.2017 um 18:23 schrieb Milamber:
> >>>>
> >>>>> Hello,
> >>>>>
> >>>>> The second release candidate for JMeter 3.2 (r1789808) has been
> >>>>> prepared, and your votes are solicited.
> >>>>>
> >>>>> This release brings new features and fixes bugs.
> >>>>>
> >>>>> Please, test this release candidate (with load tests and/or
> functional
> >>>>> tests) using Java 8 on Linux/Windows/Mac OS, especially on the
> changes.
> >>>>> The feedback are welcome.
> >>>>>
> >>>>> You can read the New and Noteworthy section with some screenshots to
> >>>>> illustrate improvements and full list of changes at:
> >>>>> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html
> >>>>>
> >>>>> JMeter is a Java desktop application designed to load test functional
> >>>>> behavior and measure performance. The current version is targeted at
> >>>>> Java 8+.
> >>>>>
> >>>>> Download - Archives/hashes/sigs:
> >>>>>
> >>>>> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
> >>>>> (dist revision r18998)
> >>>>>
> >>>>> RAT report:
> >>>>>
> >>>>> http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-repo
> >>>>> rt-jmeter-3.2RC2.txt
> >>>

Re: [VOTE] Release JMeter 3.2 RC2

[Philippe Mouawad]

Hello,
Thanks Milamber for your work on RM for this.

Due to issue reported my vote is:

[X] I do not support this release

I can fix issue if ok for you to commit in trunk.

Regards

On Sunday, April 2, 2017, Philippe Mouawad 
wrote:

> Hello,
> I am to blame for this issue, sorry !
> http://svn.apache.org/viewvc?rev=1783666=rev
>
>
> Regards
>
>
> On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
> supp...@ubikloadpack.com
> > wrote:
>
>> Hello,
>> Note this is annoying as fixing it would mean that our plugin would only
>> support 3.2.
>> We usually try to support N and N-1 versions to allow for migration.
>> And this was usually the policy with JMeter releases.
>>
>> Hope you can take this into account.
>> Regards
>>
>>
>>
>>
>> On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
>> supp...@ubikloadpack.com
>> > wrote:
>>
>>> Hello,
>>> First thanks a lot for all the team for the great work on Apache JMeter
>>> and thanks to RM !
>>>
>>> Now for this release, it appears HeaderManager API has been modified in
>>> a breaking and undocumented way:
>>> This method:
>>>
>>>- https://github.com/apache/jmeter/blob/v3_1/src/protocol/http
>>>/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268
>>>
>>> 
>>>
>>> Has been modified:
>>>
>>>- https://github.com/apache/jmeter/blob/v3_2_RC2/src/protocol/
>>>http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L234
>>>
>>> 
>>>
>>>
>>> This would unfortunately break our plugin.
>>>
>>> Is is possible to reintroduce this method and make it deprecated ?
>>>
>>> Thanks
>>> Regards
>>>
>>> UbikLoadPack Team
>>>
>>>
>>>
>>> On Sun, Apr 2, 2017 at 12:45 PM, Rainer Jung >> > wrote:
>>>
 Am 01.04.2017 um 18:23 schrieb Milamber:

> Hello,
>
> The second release candidate for JMeter 3.2 (r1789808) has been
> prepared, and your votes are solicited.
>
> This release brings new features and fixes bugs.
>
> Please, test this release candidate (with load tests and/or functional
> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
> The feedback are welcome.
>
> You can read the New and Noteworthy section with some screenshots to
> illustrate improvements and full list of changes at:
> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html
>
> JMeter is a Java desktop application designed to load test functional
> behavior and measure performance. The current version is targeted at
> Java 8+.
>
> Download - Archives/hashes/sigs:
>
> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
> (dist revision r18998)
>
> RAT report:
>
> http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-repo
> rt-jmeter-3.2RC2.txt
>
>
> MD5 hashes of archives for this vote:
>
> cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
> 5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
> 2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
> 43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip
>
> Site Docs are here:
> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/
>
> Maven staging repository is accessible here:
> https://repository.apache.org/content/repositories/orgapache
> jmeter-1016/org/apache/jmeter/
>
>
> Tag:
> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/
>
> Keys are here:
> https://www.apache.org/dist/jmeter/KEYS
>
> N.B.
> To download the dependencies: "ant download_jars"
>
> To create the jars and test JMeter: "ant package test".
>
> JMeter 3.2 requires Java 8 or later to run.
>
> Some known issues and incompatible changes are listed on changes page.
> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.
> html#Known%20problems%20and%20workarounds
>
>
>
> All feedback and vote are welcome.
>
> [XX] +1  I support this release
> [  ] +0  I am OK with this release
> [  ] -0   OK, but
> [  ] -1   I do not support this release (please indicate why)
>
> The vote will remain open for at least 72 hours.
>
> The PMC members please indicate the mention "(binding)" with your vote.
>
>
> Note: If the vote passes, the intention is to release the archive files
> and rename the RC tag as the release tag.
>
> Thanks in advance!
>

 +1 (binding), thanks for RM.

Re: [VOTE] Release JMeter 3.2 RC2

[Philippe Mouawad]

Hello,
I am to blame for this issue, sorry !
http://svn.apache.org/viewvc?rev=1783666=rev


Regards


On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
supp...@ubikloadpack.com> wrote:

> Hello,
> Note this is annoying as fixing it would mean that our plugin would only
> support 3.2.
> We usually try to support N and N-1 versions to allow for migration.
> And this was usually the policy with JMeter releases.
>
> Hope you can take this into account.
> Regards
>
>
>
>
> On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
> supp...@ubikloadpack.com> wrote:
>
>> Hello,
>> First thanks a lot for all the team for the great work on Apache JMeter
>> and thanks to RM !
>>
>> Now for this release, it appears HeaderManager API has been modified in a
>> breaking and undocumented way:
>> This method:
>>
>>- https://github.com/apache/jmeter/blob/v3_1/src/protocol/http
>>/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268
>>
>> 
>>
>> Has been modified:
>>
>>- https://github.com/apache/jmeter/blob/v3_2_RC2/src/protocol/
>>http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L234
>>
>> 
>>
>>
>> This would unfortunately break our plugin.
>>
>> Is is possible to reintroduce this method and make it deprecated ?
>>
>> Thanks
>> Regards
>>
>> UbikLoadPack Team
>>
>>
>>
>> On Sun, Apr 2, 2017 at 12:45 PM, Rainer Jung 
>> wrote:
>>
>>> Am 01.04.2017 um 18:23 schrieb Milamber:
>>>
 Hello,

 The second release candidate for JMeter 3.2 (r1789808) has been
 prepared, and your votes are solicited.

 This release brings new features and fixes bugs.

 Please, test this release candidate (with load tests and/or functional
 tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
 The feedback are welcome.

 You can read the New and Noteworthy section with some screenshots to
 illustrate improvements and full list of changes at:
 http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html

 JMeter is a Java desktop application designed to load test functional
 behavior and measure performance. The current version is targeted at
 Java 8+.

 Download - Archives/hashes/sigs:

 https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
 (dist revision r18998)

 RAT report:

 http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-repo
 rt-jmeter-3.2RC2.txt


 MD5 hashes of archives for this vote:

 cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
 5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
 2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
 43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip

 Site Docs are here:
 http://home.apache.org/~milamber/jmeter-3.2RC2/docs/

 Maven staging repository is accessible here:
 https://repository.apache.org/content/repositories/orgapache
 jmeter-1016/org/apache/jmeter/


 Tag:
 https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/

 Keys are here:
 https://www.apache.org/dist/jmeter/KEYS

 N.B.
 To download the dependencies: "ant download_jars"

 To create the jars and test JMeter: "ant package test".

 JMeter 3.2 requires Java 8 or later to run.

 Some known issues and incompatible changes are listed on changes page.
 http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.
 html#Known%20problems%20and%20workarounds



 All feedback and vote are welcome.

 [XX] +1  I support this release
 [  ] +0  I am OK with this release
 [  ] -0   OK, but
 [  ] -1   I do not support this release (please indicate why)

 The vote will remain open for at least 72 hours.

 The PMC members please indicate the mention "(binding)" with your vote.


 Note: If the vote passes, the intention is to release the archive files
 and rename the RC tag as the release tag.

 Thanks in advance!

>>>
>>> +1 (binding), thanks for RM.
>>>
>>> Details:
>>>
>>> - MD5 OK
>>> - signatures OK
>>> - key in KEYS file
>>> - tgz and zip for src and bin consistent
>>> - svn and tgz/zip mostly consistent
>>>   - file bin/utility.groovy missing in src tgz/zip
>>> IMHO not a showstopper, fixed in r1789871 after RC2.
>>> Note: the missing file breaks the ability to run
>>> "ant distribution" from a src tgz/zip.
>>> I think this must have already been the case for
>>> 3.1 (untested).
>>>   - some files with name "*cp1252*" contain some binary differences
>>> between svn and zip.
>>> Example: file 

Re: [VOTE] Release JMeter 3.2 RC2

[UBIK LOAD PACK Support]

Hello,
Note this is annoying as fixing it would mean that our plugin would only
support 3.2.
We usually try to support N and N-1 versions to allow for migration.
And this was usually the policy with JMeter releases.

Hope you can take this into account.
Regards



On Sun, Apr 2, 2017 at 3:03 PM, UBIK LOAD PACK Support <
supp...@ubikloadpack.com> wrote:

> Hello,
> First thanks a lot for all the team for the great work on Apache JMeter
> and thanks to RM !
>
> Now for this release, it appears HeaderManager API has been modified in a
> breaking and undocumented way:
> This method:
>
>- https://github.com/apache/jmeter/blob/v3_1/src/protocol/
>http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268
>
> 
>
> Has been modified:
>
>- https://github.com/apache/jmeter/blob/v3_2_RC2/src/
>protocol/http/org/apache/jmeter/protocol/http/control/
>HeaderManager.java#L234
>
> 
>
>
> This would unfortunately break our plugin.
>
> Is is possible to reintroduce this method and make it deprecated ?
>
> Thanks
> Regards
>
> UbikLoadPack Team
>
>
>
> On Sun, Apr 2, 2017 at 12:45 PM, Rainer Jung 
> wrote:
>
>> Am 01.04.2017 um 18:23 schrieb Milamber:
>>
>>> Hello,
>>>
>>> The second release candidate for JMeter 3.2 (r1789808) has been
>>> prepared, and your votes are solicited.
>>>
>>> This release brings new features and fixes bugs.
>>>
>>> Please, test this release candidate (with load tests and/or functional
>>> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
>>> The feedback are welcome.
>>>
>>> You can read the New and Noteworthy section with some screenshots to
>>> illustrate improvements and full list of changes at:
>>> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html
>>>
>>> JMeter is a Java desktop application designed to load test functional
>>> behavior and measure performance. The current version is targeted at
>>> Java 8+.
>>>
>>> Download - Archives/hashes/sigs:
>>>
>>> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
>>> (dist revision r18998)
>>>
>>> RAT report:
>>>
>>> http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-repo
>>> rt-jmeter-3.2RC2.txt
>>>
>>>
>>> MD5 hashes of archives for this vote:
>>>
>>> cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
>>> 5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
>>> 2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
>>> 43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip
>>>
>>> Site Docs are here:
>>> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/
>>>
>>> Maven staging repository is accessible here:
>>> https://repository.apache.org/content/repositories/orgapache
>>> jmeter-1016/org/apache/jmeter/
>>>
>>>
>>> Tag:
>>> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/
>>>
>>> Keys are here:
>>> https://www.apache.org/dist/jmeter/KEYS
>>>
>>> N.B.
>>> To download the dependencies: "ant download_jars"
>>>
>>> To create the jars and test JMeter: "ant package test".
>>>
>>> JMeter 3.2 requires Java 8 or later to run.
>>>
>>> Some known issues and incompatible changes are listed on changes page.
>>> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.
>>> html#Known%20problems%20and%20workarounds
>>>
>>>
>>>
>>> All feedback and vote are welcome.
>>>
>>> [XX] +1  I support this release
>>> [  ] +0  I am OK with this release
>>> [  ] -0   OK, but
>>> [  ] -1   I do not support this release (please indicate why)
>>>
>>> The vote will remain open for at least 72 hours.
>>>
>>> The PMC members please indicate the mention "(binding)" with your vote.
>>>
>>>
>>> Note: If the vote passes, the intention is to release the archive files
>>> and rename the RC tag as the release tag.
>>>
>>> Thanks in advance!
>>>
>>
>> +1 (binding), thanks for RM.
>>
>> Details:
>>
>> - MD5 OK
>> - signatures OK
>> - key in KEYS file
>> - tgz and zip for src and bin consistent
>> - svn and tgz/zip mostly consistent
>>   - file bin/utility.groovy missing in src tgz/zip
>> IMHO not a showstopper, fixed in r1789871 after RC2.
>> Note: the missing file breaks the ability to run
>> "ant distribution" from a src tgz/zip.
>> I think this must have already been the case for
>> 3.1 (untested).
>>   - some files with name "*cp1252*" contain some binary differences
>> between svn and zip.
>> Example: file test/resources/org/apache/jmet
>> er/protocol/jms/sampler/render/cp1252.txt
>> in svn is 3 bytes hex 0xe9 0xe8 0x80
>> and in zip 6 bytes hex 0xef 0xbf 0xbd 0xef 0xbf 0xbd
>> - files bin/report-template/*/*/*/make.sh are not executable
>>   (not in svn and not in any bin or src archive)
>> - builds fine except:
>>   - needed to disable class 

Re: [VOTE] Release JMeter 3.2 RC2

[UBIK LOAD PACK Support]

Hello,
First thanks a lot for all the team for the great work on Apache JMeter and
thanks to RM !

Now for this release, it appears HeaderManager API has been modified in a
breaking and undocumented way:
This method:

   -
   
https://github.com/apache/jmeter/blob/v3_1/src/protocol/http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L268

Has been modified:

   -
   
https://github.com/apache/jmeter/blob/v3_2_RC2/src/protocol/http/org/apache/jmeter/protocol/http/control/HeaderManager.java#L234


This would unfortunately break our plugin.

Is is possible to reintroduce this method and make it deprecated ?

Thanks
Regards

UbikLoadPack Team



On Sun, Apr 2, 2017 at 12:45 PM, Rainer Jung 
wrote:

> Am 01.04.2017 um 18:23 schrieb Milamber:
>
>> Hello,
>>
>> The second release candidate for JMeter 3.2 (r1789808) has been
>> prepared, and your votes are solicited.
>>
>> This release brings new features and fixes bugs.
>>
>> Please, test this release candidate (with load tests and/or functional
>> tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
>> The feedback are welcome.
>>
>> You can read the New and Noteworthy section with some screenshots to
>> illustrate improvements and full list of changes at:
>> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html
>>
>> JMeter is a Java desktop application designed to load test functional
>> behavior and measure performance. The current version is targeted at
>> Java 8+.
>>
>> Download - Archives/hashes/sigs:
>>
>> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
>> (dist revision r18998)
>>
>> RAT report:
>>
>> http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-
>> report-jmeter-3.2RC2.txt
>>
>>
>> MD5 hashes of archives for this vote:
>>
>> cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
>> 5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
>> 2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
>> 43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip
>>
>> Site Docs are here:
>> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/
>>
>> Maven staging repository is accessible here:
>> https://repository.apache.org/content/repositories/orgapache
>> jmeter-1016/org/apache/jmeter/
>>
>>
>> Tag:
>> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/
>>
>> Keys are here:
>> https://www.apache.org/dist/jmeter/KEYS
>>
>> N.B.
>> To download the dependencies: "ant download_jars"
>>
>> To create the jars and test JMeter: "ant package test".
>>
>> JMeter 3.2 requires Java 8 or later to run.
>>
>> Some known issues and incompatible changes are listed on changes page.
>> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.
>> html#Known%20problems%20and%20workarounds
>>
>>
>>
>> All feedback and vote are welcome.
>>
>> [XX] +1  I support this release
>> [  ] +0  I am OK with this release
>> [  ] -0   OK, but
>> [  ] -1   I do not support this release (please indicate why)
>>
>> The vote will remain open for at least 72 hours.
>>
>> The PMC members please indicate the mention "(binding)" with your vote.
>>
>>
>> Note: If the vote passes, the intention is to release the archive files
>> and rename the RC tag as the release tag.
>>
>> Thanks in advance!
>>
>
> +1 (binding), thanks for RM.
>
> Details:
>
> - MD5 OK
> - signatures OK
> - key in KEYS file
> - tgz and zip for src and bin consistent
> - svn and tgz/zip mostly consistent
>   - file bin/utility.groovy missing in src tgz/zip
> IMHO not a showstopper, fixed in r1789871 after RC2.
> Note: the missing file breaks the ability to run
> "ant distribution" from a src tgz/zip.
> I think this must have already been the case for
> 3.1 (untested).
>   - some files with name "*cp1252*" contain some binary differences
> between svn and zip.
> Example: file test/resources/org/apache/jmet
> er/protocol/jms/sampler/render/cp1252.txt
> in svn is 3 bytes hex 0xe9 0xe8 0x80
> and in zip 6 bytes hex 0xef 0xbf 0xbd 0xef 0xbf 0xbd
> - files bin/report-template/*/*/*/make.sh are not executable
>   (not in svn and not in any bin or src archive)
> - builds fine except:
>   - needed to disable class RenderInBrowser.java,
> because Oracle doesn't support JavaFX for Solaris
> - build result looks consistent with distribution, except for
>   - some ordering in javadoc (expected)
>   - binary jar files (expected)
> - no Javadoc warnings
> - new dependencies (expected)
> - ran the tests (but only with java.awt.headless) without failures
>   - needed to adjust the 500ms test execution time margin in
> TestSchedulerWithTimer.jmx (slow test system)
> - I have not checked the staging repository.
> - I have not checked the rat report
>
> Build and tests were done using Java 1.8.0_121, OS was Solaris 10 Sparc.
>
> Regards,
>
> Rainer
>

Re: [VOTE] Release JMeter 3.2 RC2

[Rainer Jung]

Am 01.04.2017 um 18:23 schrieb Milamber:

Hello,

The second release candidate for JMeter 3.2 (r1789808) has been
prepared, and your votes are solicited.

This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional
tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes.
The feedback are welcome.

You can read the New and Noteworthy section with some screenshots to
illustrate improvements and full list of changes at:
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html

JMeter is a Java desktop application designed to load test functional
behavior and measure performance. The current version is targeted at
Java 8+.

Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
(dist revision r18998)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-report-jmeter-3.2RC2.txt


MD5 hashes of archives for this vote:

cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1016/org/apache/jmeter/


Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html#Known%20problems%20and%20workarounds



All feedback and vote are welcome.

[XX] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!


+1 (binding), thanks for RM.

Details:

- MD5 OK
- signatures OK
- key in KEYS file
- tgz and zip for src and bin consistent
- svn and tgz/zip mostly consistent
  - file bin/utility.groovy missing in src tgz/zip
IMHO not a showstopper, fixed in r1789871 after RC2.
Note: the missing file breaks the ability to run
"ant distribution" from a src tgz/zip.
I think this must have already been the case for
3.1 (untested).
  - some files with name "*cp1252*" contain some binary differences
between svn and zip.
Example: file 
test/resources/org/apache/jmeter/protocol/jms/sampler/render/cp1252.txt

in svn is 3 bytes hex 0xe9 0xe8 0x80
and in zip 6 bytes hex 0xef 0xbf 0xbd 0xef 0xbf 0xbd
- files bin/report-template/*/*/*/make.sh are not executable
  (not in svn and not in any bin or src archive)
- builds fine except:
  - needed to disable class RenderInBrowser.java,
because Oracle doesn't support JavaFX for Solaris
- build result looks consistent with distribution, except for
  - some ordering in javadoc (expected)
  - binary jar files (expected)
- no Javadoc warnings
- new dependencies (expected)
- ran the tests (but only with java.awt.headless) without failures
  - needed to adjust the 500ms test execution time margin in
TestSchedulerWithTimer.jmx (slow test system)
- I have not checked the staging repository.
- I have not checked the rat report

Build and tests were done using Java 1.8.0_121, OS was Solaris 10 Sparc.

Regards,

Rainer

Re: [VOTE] Release JMeter 3.2 RC2

[Andrey Pokhilko]

+1

Andrey Pokhilko

On 01.04.2017 19:23, Milamber wrote:
> Hello,
>
> The second release candidate for JMeter 3.2 (r1789808) has been
> prepared, and your votes are solicited.
>
> This release brings new features and fixes bugs.
>
> Please, test this release candidate (with load tests and/or functional
> tests) using Java 8 on Linux/Windows/Mac OS, especially on the
> changes. The feedback are welcome.
>
> You can read the New and Noteworthy section with some screenshots to
> illustrate improvements and full list of changes at:
> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html
>
> JMeter is a Java desktop application designed to load test functional
> behavior and measure performance. The current version is targeted at
> Java 8+.
>
> Download - Archives/hashes/sigs:
>
> https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
> (dist revision r18998)
>
> RAT report:
>
> http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-report-jmeter-3.2RC2.txt
>
>
> MD5 hashes of archives for this vote:
>
> cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
> 5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
> 2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
> 43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip
>
> Site Docs are here:
> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/
>
> Maven staging repository is accessible here:
> https://repository.apache.org/content/repositories/orgapachejmeter-1016/org/apache/jmeter/
>
>
> Tag:
> https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/
>
> Keys are here:
> https://www.apache.org/dist/jmeter/KEYS
>
> N.B.
> To download the dependencies: "ant download_jars"
>
> To create the jars and test JMeter: "ant package test".
>
> JMeter 3.2 requires Java 8 or later to run.
>
> Some known issues and incompatible changes are listed on changes page.
> http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html#Known%20problems%20and%20workarounds
>
>
>
> All feedback and vote are welcome.
> 
> [  ] +1  I support this release
> [  ] +0  I am OK with this release
> [  ] -0   OK, but
> [  ] -1   I do not support this release (please indicate why)
>
> The vote will remain open for at least 72 hours.
>
> The PMC members please indicate the mention "(binding)" with your vote.
>
>
> Note: If the vote passes, the intention is to release the archive files
> and rename the RC tag as the release tag.
>
> Thanks in advance!
>
> Milamber
>
>
>
>
>
>

RE: [VOTE] Release JMeter 3.2 RC2

[catchnaveen . psgtech]

+1

-Original Message-
From: Milamber [mailto:milam...@apache.org] 
Sent: Saturday, April 1, 2017 11:23 AM
To: JMeter Dev List <dev@jmeter.apache.org>
Subject: [VOTE] Release JMeter 3.2 RC2

Hello,

The second release candidate for JMeter 3.2 (r1789808) has been prepared, and 
your votes are solicited.

This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional
tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes. 
The feedback are welcome.

You can read the New and Noteworthy section with some screenshots to illustrate 
improvements and full list of changes at:
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html

JMeter is a Java desktop application designed to load test functional behavior 
and measure performance. The current version is targeted at Java 8+.

Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
(dist revision r18998)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-report-jmeter-3.2RC2.txt

MD5 hashes of archives for this vote:

cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip 
2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1016/org/apache/jmeter/

Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html#Known%20problems%20and%20workarounds


All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files and 
rename the RC tag as the release tag.

Thanks in advance!

Milamber

[VOTE] Release JMeter 3.2 RC2

[Milamber]

Hello,

The second release candidate for JMeter 3.2 (r1789808) has been 
prepared, and your votes are solicited.


This release brings new features and fixes bugs.

Please, test this release candidate (with load tests and/or functional 
tests) using Java 8 on Linux/Windows/Mac OS, especially on the changes. 
The feedback are welcome.


You can read the New and Noteworthy section with some screenshots to 
illustrate improvements and full list of changes at:

http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html

JMeter is a Java desktop application designed to load test functional 
behavior and measure performance. The current version is targeted at 
Java 8+.


Download - Archives/hashes/sigs:

https://dist.apache.org/repos/dist/dev/jmeter/v3.2_RC2/
(dist revision r18998)

RAT report:

http://home.apache.org/~milamber/jmeter-3.2RC2/dist/rat-report-jmeter-3.2RC2.txt

MD5 hashes of archives for this vote:

cfa8095f9c42208eb70caa6a0074558a *apache-jmeter-3.2.tgz
5d49a7cf94ce4dfebc68ab35f6f686d8 *apache-jmeter-3.2.zip
2dad5f6366647c93f822c87e64ff24ac *apache-jmeter-3.2_src.tgz
43f4ea27110efb23032e708e44dafe55 *apache-jmeter-3.2_src.zip

Site Docs are here:
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/

Maven staging repository is accessible here:
https://repository.apache.org/content/repositories/orgapachejmeter-1016/org/apache/jmeter/

Tag:
https://svn.apache.org/repos/asf/jmeter/tags/v3_2_RC2/

Keys are here:
https://www.apache.org/dist/jmeter/KEYS

N.B.
To download the dependencies: "ant download_jars"

To create the jars and test JMeter: "ant package test".

JMeter 3.2 requires Java 8 or later to run.

Some known issues and incompatible changes are listed on changes page.
http://home.apache.org/~milamber/jmeter-3.2RC2/docs/changes.html#Known%20problems%20and%20workarounds


All feedback and vote are welcome.

[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release (please indicate why)

The vote will remain open for at least 72 hours.

The PMC members please indicate the mention "(binding)" with your vote.


Note: If the vote passes, the intention is to release the archive files
and rename the RC tag as the release tag.

Thanks in advance!

Milamber

Re: Release a 3.2

[Philippe Mouawad]

Hello,
It would be great.
No blocking bug for release Afaik.

But a review of last fixes on http pool connection leak would be welcome.

Regards

On Wednesday, March 29, 2017, Milamber <milam...@apache.org> wrote:

>
> I can start a RC for this Saturday, that's possible? any bug to fix before?
>
>
> On 28/03/2017 10:07, Maxime Chassagneux wrote:
>
>> +1
>>
>> 2017-03-28 10:13 GMT+02:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:
>>
>> +1
>>>
>>> Antonio
>>>
>>> 2017-03-27 22:34 GMT+02:00 Philippe Mouawad <philippe.moua...@gmail.com
>>> >:
>>>
>>> Hello,
>>>> Shall we start the 3.2 release process now that all points have been
>>>> handled ?
>>>>
>>>> Regards
>>>>
>>>> On Sun, Mar 26, 2017 at 6:26 PM, Philippe Mouawad <
>>>> philippe.moua...@gmail.com> wrote:
>>>>
>>>> Thanks a lot Woonsan, merged.
>>>>>
>>>>> On Sun, Mar 26, 2017 at 6:32 AM, Woonsan Ko <woon...@apache.org>
>>>>>
>>>> wrote:
>>>
>>>> On Fri, Mar 24, 2017 at 10:39 AM, Woonsan Ko <woon...@apache.org>
>>>>>>
>>>>> wrote:
>>>>
>>>>> On Mon, Mar 20, 2017 at 7:05 PM, sebb <seb...@gmail.com> wrote:
>>>>>>>
>>>>>>>> On 20 March 2017 at 22:57, Philippe Mouawad <
>>>>>>>>
>>>>>>> philippe.moua...@gmail.com> wrote:
>>>>>>
>>>>>>> On Monday, March 20, 2017, sebb <seb...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> I know I keep going on about this, but the logging documentation
>>>>>>>>>>
>>>>>>>>> still
>>>>>>
>>>>>>> needs some work.
>>>>>>>>>>
>>>>>>>>>> The logging level names have changed.
>>>>>>>>>> Users need to be told what the mapping is from old name to new
>>>>>>>>>>
>>>>>>>>> name.
>>>>
>>>>> cf comments on r1786590
>>>>>>>>>>
>>>>>>>>> Work has been done since that time.
>>>>>>>>> Please point to missing information.
>>>>>>>>>
>>>>>>>> Where are the logging levels documented?
>>>>>>>> I had a quick look and could not find them.
>>>>>>>>
>>>>>>> I've submitted a PR: https://github.com/apache/jmeter/pull/286
>>>>>> Please take a look.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Woonsan
>>>>>>
>>>>>> Sorry for late response. I'll try to submit a pull request to
>>>>>>>
>>>>>> clarify
>>>
>>>> the changes of the available log levels before Monday.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Woosnan
>>>>>>>
>>>>>>>
>>>>>>>>>> On 20 March 2017 at 22:26, Antonio Gomes Rodrigues <
>>>>>>>>>>
>>>>>>>>> ra0...@gmail.com
>>>>
>>>>> <javascript:;>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> Antonio
>>>>>>>>>>>
>>>>>>>>>>> 2017-03-20 21:49 GMT+01:00 Philippe Mouawad <
>>>>>>>>>>>
>>>>>>>>>> philippe.moua...@gmail.com
>>>>>>
>>>>>>> <javascript:;>>:
>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>> AFAIU, there are no more pending points for a release.
>>>>>>>>>>>>
>>>>>>>>>>>> Am I wrong ?
>>>>>>>>>>>> If not, could be start a release ?
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> Regards
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>

Re: Release a 3.2

[Milamber]

I can start a RC for this Saturday, that's possible? any bug to fix before?


On 28/03/2017 10:07, Maxime Chassagneux wrote:

+1

2017-03-28 10:13 GMT+02:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:


+1

Antonio

2017-03-27 22:34 GMT+02:00 Philippe Mouawad <philippe.moua...@gmail.com>:


Hello,
Shall we start the 3.2 release process now that all points have been
handled ?

Regards

On Sun, Mar 26, 2017 at 6:26 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:


Thanks a lot Woonsan, merged.

On Sun, Mar 26, 2017 at 6:32 AM, Woonsan Ko <woon...@apache.org>

wrote:

On Fri, Mar 24, 2017 at 10:39 AM, Woonsan Ko <woon...@apache.org>

wrote:

On Mon, Mar 20, 2017 at 7:05 PM, sebb <seb...@gmail.com> wrote:

On 20 March 2017 at 22:57, Philippe Mouawad <

philippe.moua...@gmail.com> wrote:

On Monday, March 20, 2017, sebb <seb...@gmail.com> wrote:


I know I keep going on about this, but the logging documentation

still

needs some work.

The logging level names have changed.
Users need to be told what the mapping is from old name to new

name.

cf comments on r1786590

Work has been done since that time.
Please point to missing information.

Where are the logging levels documented?
I had a quick look and could not find them.

I've submitted a PR: https://github.com/apache/jmeter/pull/286
Please take a look.

Regards,

Woonsan


Sorry for late response. I'll try to submit a pull request to

clarify

the changes of the available log levels before Monday.

Regards,

Woosnan



On 20 March 2017 at 22:26, Antonio Gomes Rodrigues <

ra0...@gmail.com

<javascript:;>> wrote:

+1

Antonio

2017-03-20 21:49 GMT+01:00 Philippe Mouawad <

philippe.moua...@gmail.com

<javascript:;>>:

Hello,
AFAIU, there are no more pending points for a release.

Am I wrong ?
If not, could be start a release ?
Thanks
Regards


On Thu, Mar 16, 2017 at 11:43 PM, Antonio Gomes Rodrigues <
ra0...@gmail.com <javascript:;>>
wrote:


Hi,

I have updated jmeter_accesslog_sampler_step_by_step

document

like I

have

said previously

Antonio

2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru

<javascript:;>

:

We have fixed them and released plugin updates. For the

record, it

were:

   * OAuth Sampler broken - we decided to deprecate it
   * JMX Check tool were failing on call to removed
 "org.apache.jmeter.save.SaveService.loadTree(

InputStream

 inputStream)", we've released update with other method

used

   * Synthesis report were failing on call to modified
 "org.apache.jmeter.save.CSVSaveService#saveCSVStats(

java.util.List,

 java.io.FileWriter, java.lang.String[])", we've

released

update

that

 uses different method
   * BlazeMeter Debugger plugin fails due to changes to

LoggerPanel

and

 several other changes around logging, we have no good

solution

for

 now, that will work on both JMeter 3.1 and 3.2. We

need

more

time

to

 work on it and we don't consider it as release

blocker.

Andrey Pokhilko

On 16.03.2017 16:03, Philippe Mouawad wrote:

What are the other "number of issues " ?
Thanks

On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <

a...@ya.ru

<javascript:;>> wrote:

Hi,

Yes, it's that message. The bugzilla is here:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60874

Andrey Pokhilko

On 16.03.2017 16:01, Philippe Mouawad wrote:

Hello Andrey,
Thanks for your tests.
We're waiting for the Bugzilla, is it the issue

mentioned

by

somebody

on

mailing list about a constant for Scripting languages

?

Thanks
Regards

On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <

a...@ya.ru

<javascript:;>>

wrote:

Hi,

 From plugins side, we've made check in BlazeMeter and

found a

number

of

issues, mainly because of deleted methods and fields.

We

have

fixed

some

of them, but one is specifically breaking WebDriver

sampler.

We're

going

to file bugzilla on it.

IMO it's not good to release without fixing this,

since

it will

break

everyone who uses WebDriver Sampler.

Andrey Pokhilko

On 16.03.2017 15:32, Philippe Mouawad wrote:

Hello,
Any feedback on patch ?
Shall we proceed with release without fixing it ?
Is there any other remaining work ?

Thanks
Regards
Philippe

On Sunday, March 12, 2017, Philippe Mouawad <

philippe.moua...@gmail.com <javascript:;>>

wrote:


Hello,
I've filled New and Noteworthy section, feel free

to

improve.

I've also documented migration to new logging.

I think we can now release the 3.2 except for this

bug

which

exists

since

many versions, I've attached a patch for review:
- https://bz.apache.org/

bugzilla/show_bug.cgi?id=60830

Regards

On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes

Rodrigues <

ra0...@gmail.com <javascript:;>

<javascript:_e(%7B%7D,'cvml','ra0...@gmail.com

<javascript:;>');>> wrote:

Hi,

Modifications in the PR done

Anto

Re: Release a 3.2

[Maxime Chassagneux]

+1

2017-03-28 10:13 GMT+02:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:

> +1
>
> Antonio
>
> 2017-03-27 22:34 GMT+02:00 Philippe Mouawad <philippe.moua...@gmail.com>:
>
> > Hello,
> > Shall we start the 3.2 release process now that all points have been
> > handled ?
> >
> > Regards
> >
> > On Sun, Mar 26, 2017 at 6:26 PM, Philippe Mouawad <
> > philippe.moua...@gmail.com> wrote:
> >
> > > Thanks a lot Woonsan, merged.
> > >
> > > On Sun, Mar 26, 2017 at 6:32 AM, Woonsan Ko <woon...@apache.org>
> wrote:
> > >
> > >> On Fri, Mar 24, 2017 at 10:39 AM, Woonsan Ko <woon...@apache.org>
> > wrote:
> > >> > On Mon, Mar 20, 2017 at 7:05 PM, sebb <seb...@gmail.com> wrote:
> > >> >> On 20 March 2017 at 22:57, Philippe Mouawad <
> > >> philippe.moua...@gmail.com> wrote:
> > >> >>> On Monday, March 20, 2017, sebb <seb...@gmail.com> wrote:
> > >> >>>
> > >> >>>> I know I keep going on about this, but the logging documentation
> > >> still
> > >> >>>> needs some work.
> > >> >>>>
> > >> >>>> The logging level names have changed.
> > >> >>>> Users need to be told what the mapping is from old name to new
> > name.
> > >> >>>>
> > >> >>>> cf comments on r1786590
> > >> >>>
> > >> >>> Work has been done since that time.
> > >> >>> Please point to missing information.
> > >> >>
> > >> >> Where are the logging levels documented?
> > >> >> I had a quick look and could not find them.
> > >> I've submitted a PR: https://github.com/apache/jmeter/pull/286
> > >> Please take a look.
> > >>
> > >> Regards,
> > >>
> > >> Woonsan
> > >>
> > >> >
> > >> > Sorry for late response. I'll try to submit a pull request to
> clarify
> > >> > the changes of the available log levels before Monday.
> > >> >
> > >> > Regards,
> > >> >
> > >> > Woosnan
> > >> >
> > >> >>
> > >> >>>
> > >> >>>>
> > >> >>>>
> > >> >>>> On 20 March 2017 at 22:26, Antonio Gomes Rodrigues <
> > ra0...@gmail.com
> > >> >>>> <javascript:;>> wrote:
> > >> >>>> > +1
> > >> >>>> >
> > >> >>>> > Antonio
> > >> >>>> >
> > >> >>>> > 2017-03-20 21:49 GMT+01:00 Philippe Mouawad <
> > >> philippe.moua...@gmail.com
> > >> >>>> <javascript:;>>:
> > >> >>>> >
> > >> >>>> >> Hello,
> > >> >>>> >> AFAIU, there are no more pending points for a release.
> > >> >>>> >>
> > >> >>>> >> Am I wrong ?
> > >> >>>> >> If not, could be start a release ?
> > >> >>>> >> Thanks
> > >> >>>> >> Regards
> > >> >>>> >>
> > >> >>>> >>
> > >> >>>> >> On Thu, Mar 16, 2017 at 11:43 PM, Antonio Gomes Rodrigues <
> > >> >>>> >> ra0...@gmail.com <javascript:;>>
> > >> >>>> >> wrote:
> > >> >>>> >>
> > >> >>>> >> > Hi,
> > >> >>>> >> >
> > >> >>>> >> > I have updated jmeter_accesslog_sampler_step_by_step
> document
> > >> like I
> > >> >>>> >> have
> > >> >>>> >> > said previously
> > >> >>>> >> >
> > >> >>>> >> > Antonio
> > >> >>>> >> >
> > >> >>>> >> > 2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru
> > >> <javascript:;>
> > >> >>>> >:
> > >> >>>> >> >
> > >> >>>> >> > > We have fixed them and released plugin updates. For the
> > >> record, it
>

Re: Release a 3.2

[Antonio Gomes Rodrigues]

+1

Antonio

2017-03-27 22:34 GMT+02:00 Philippe Mouawad <philippe.moua...@gmail.com>:

> Hello,
> Shall we start the 3.2 release process now that all points have been
> handled ?
>
> Regards
>
> On Sun, Mar 26, 2017 at 6:26 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
> > Thanks a lot Woonsan, merged.
> >
> > On Sun, Mar 26, 2017 at 6:32 AM, Woonsan Ko <woon...@apache.org> wrote:
> >
> >> On Fri, Mar 24, 2017 at 10:39 AM, Woonsan Ko <woon...@apache.org>
> wrote:
> >> > On Mon, Mar 20, 2017 at 7:05 PM, sebb <seb...@gmail.com> wrote:
> >> >> On 20 March 2017 at 22:57, Philippe Mouawad <
> >> philippe.moua...@gmail.com> wrote:
> >> >>> On Monday, March 20, 2017, sebb <seb...@gmail.com> wrote:
> >> >>>
> >> >>>> I know I keep going on about this, but the logging documentation
> >> still
> >> >>>> needs some work.
> >> >>>>
> >> >>>> The logging level names have changed.
> >> >>>> Users need to be told what the mapping is from old name to new
> name.
> >> >>>>
> >> >>>> cf comments on r1786590
> >> >>>
> >> >>> Work has been done since that time.
> >> >>> Please point to missing information.
> >> >>
> >> >> Where are the logging levels documented?
> >> >> I had a quick look and could not find them.
> >> I've submitted a PR: https://github.com/apache/jmeter/pull/286
> >> Please take a look.
> >>
> >> Regards,
> >>
> >> Woonsan
> >>
> >> >
> >> > Sorry for late response. I'll try to submit a pull request to clarify
> >> > the changes of the available log levels before Monday.
> >> >
> >> > Regards,
> >> >
> >> > Woosnan
> >> >
> >> >>
> >> >>>
> >> >>>>
> >> >>>>
> >> >>>> On 20 March 2017 at 22:26, Antonio Gomes Rodrigues <
> ra0...@gmail.com
> >> >>>> <javascript:;>> wrote:
> >> >>>> > +1
> >> >>>> >
> >> >>>> > Antonio
> >> >>>> >
> >> >>>> > 2017-03-20 21:49 GMT+01:00 Philippe Mouawad <
> >> philippe.moua...@gmail.com
> >> >>>> <javascript:;>>:
> >> >>>> >
> >> >>>> >> Hello,
> >> >>>> >> AFAIU, there are no more pending points for a release.
> >> >>>> >>
> >> >>>> >> Am I wrong ?
> >> >>>> >> If not, could be start a release ?
> >> >>>> >> Thanks
> >> >>>> >> Regards
> >> >>>> >>
> >> >>>> >>
> >> >>>> >> On Thu, Mar 16, 2017 at 11:43 PM, Antonio Gomes Rodrigues <
> >> >>>> >> ra0...@gmail.com <javascript:;>>
> >> >>>> >> wrote:
> >> >>>> >>
> >> >>>> >> > Hi,
> >> >>>> >> >
> >> >>>> >> > I have updated jmeter_accesslog_sampler_step_by_step document
> >> like I
> >> >>>> >> have
> >> >>>> >> > said previously
> >> >>>> >> >
> >> >>>> >> > Antonio
> >> >>>> >> >
> >> >>>> >> > 2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru
> >> <javascript:;>
> >> >>>> >:
> >> >>>> >> >
> >> >>>> >> > > We have fixed them and released plugin updates. For the
> >> record, it
> >> >>>> >> were:
> >> >>>> >> > >
> >> >>>> >> > >   * OAuth Sampler broken - we decided to deprecate it
> >> >>>> >> > >   * JMX Check tool were failing on call to removed
> >> >>>> >> > > "org.apache.jmeter.save.SaveService.loadTree(
> InputStream
> >> >>>> >> > > inputStream)", we've released update with other method
> >> used
> >> >>>> >> 

Re: Release a 3.2

[Philippe Mouawad]

t;>> >> > > On 16.03.2017 16:03, Philippe Mouawad wrote:
> >>>> >> > > > What are the other "number of issues " ?
> >>>> >> > > > Thanks
> >>>> >> > > >
> >>>> >> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru
> >>>> <javascript:;>> wrote:
> >>>> >> > > >
> >>>> >> > > >> Hi,
> >>>> >> > > >>
> >>>> >> > > >> Yes, it's that message. The bugzilla is here:
> >>>> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
> >>>> >> > > >>
> >>>> >> > > >> Andrey Pokhilko
> >>>> >> > > >>
> >>>> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
> >>>> >> > > >>> Hello Andrey,
> >>>> >> > > >>> Thanks for your tests.
> >>>> >> > > >>> We're waiting for the Bugzilla, is it the issue mentioned
> by
> >>>> >> somebody
> >>>> >> > > on
> >>>> >> > > >>> mailing list about a constant for Scripting languages ?
> >>>> >> > > >>>
> >>>> >> > > >>> Thanks
> >>>> >> > > >>> Regards
> >>>> >> > > >>>
> >>>> >> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <
> a...@ya.ru
> >>>> <javascript:;>>
> >>>> >> wrote:
> >>>> >> > > >>>
> >>>> >> > > >>>> Hi,
> >>>> >> > > >>>>
> >>>> >> > > >>>> From plugins side, we've made check in BlazeMeter and
> found a
> >>>> >> number
> >>>> >> > > of
> >>>> >> > > >>>> issues, mainly because of deleted methods and fields. We
> have
> >>>> >> fixed
> >>>> >> > > some
> >>>> >> > > >>>> of them, but one is specifically breaking WebDriver
> sampler.
> >>>> We're
> >>>> >> > > going
> >>>> >> > > >>>> to file bugzilla on it.
> >>>> >> > > >>>>
> >>>> >> > > >>>> IMO it's not good to release without fixing this, since
> it will
> >>>> >> > break
> >>>> >> > > >>>> everyone who uses WebDriver Sampler.
> >>>> >> > > >>>>
> >>>> >> > > >>>> Andrey Pokhilko
> >>>> >> > > >>>>
> >>>> >> > > >>>> On 16.03.2017 15:32, Philippe Mouawad wrote:
> >>>> >> > > >>>>> Hello,
> >>>> >> > > >>>>> Any feedback on patch ?
> >>>> >> > > >>>>> Shall we proceed with release without fixing it ?
> >>>> >> > > >>>>> Is there any other remaining work ?
> >>>> >> > > >>>>>
> >>>> >> > > >>>>> Thanks
> >>>> >> > > >>>>> Regards
> >>>> >> > > >>>>> Philippe
> >>>> >> > > >>>>>
> >>>> >> > > >>>>> On Sunday, March 12, 2017, Philippe Mouawad <
> >>>> >> > > >> philippe.moua...@gmail.com <javascript:;>>
> >>>> >> > > >>>>> wrote:
> >>>> >> > > >>>>>
> >>>> >> > > >>>>>> Hello,
> >>>> >> > > >>>>>> I've filled New and Noteworthy section, feel free to
> improve.
> >>>> >> > > >>>>>> I've also documented migration to new logging.
> >>>> >> > > >>>>>>
> >>>> >> > > >>>>>> I think we can now release the 3.2 exc

Re: Release a 3.2

[sebb]

the other "number of issues " ?
>>>>> >> > > > Thanks
>>>>> >> > > >
>>>>> >> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru
>>>>> <javascript:;>> wrote:
>>>>> >> > > >
>>>>> >> > > >> Hi,
>>>>> >> > > >>
>>>>> >> > > >> Yes, it's that message. The bugzilla is here:
>>>>> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
>>>>> >> > > >>
>>>>> >> > > >> Andrey Pokhilko
>>>>> >> > > >>
>>>>> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
>>>>> >> > > >>> Hello Andrey,
>>>>> >> > > >>> Thanks for your tests.
>>>>> >> > > >>> We're waiting for the Bugzilla, is it the issue mentioned by
>>>>> >> somebody
>>>>> >> > > on
>>>>> >> > > >>> mailing list about a constant for Scripting languages ?
>>>>> >> > > >>>
>>>>> >> > > >>> Thanks
>>>>> >> > > >>> Regards
>>>>> >> > > >>>
>>>>> >> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru
>>>>> <javascript:;>>
>>>>> >> wrote:
>>>>> >> > > >>>
>>>>> >> > > >>>> Hi,
>>>>> >> > > >>>>
>>>>> >> > > >>>> From plugins side, we've made check in BlazeMeter and found a
>>>>> >> number
>>>>> >> > > of
>>>>> >> > > >>>> issues, mainly because of deleted methods and fields. We have
>>>>> >> fixed
>>>>> >> > > some
>>>>> >> > > >>>> of them, but one is specifically breaking WebDriver sampler.
>>>>> We're
>>>>> >> > > going
>>>>> >> > > >>>> to file bugzilla on it.
>>>>> >> > > >>>>
>>>>> >> > > >>>> IMO it's not good to release without fixing this, since it 
>>>>> >> > > >>>> will
>>>>> >> > break
>>>>> >> > > >>>> everyone who uses WebDriver Sampler.
>>>>> >> > > >>>>
>>>>> >> > > >>>> Andrey Pokhilko
>>>>> >> > > >>>>
>>>>> >> > > >>>> On 16.03.2017 15:32, Philippe Mouawad wrote:
>>>>> >> > > >>>>> Hello,
>>>>> >> > > >>>>> Any feedback on patch ?
>>>>> >> > > >>>>> Shall we proceed with release without fixing it ?
>>>>> >> > > >>>>> Is there any other remaining work ?
>>>>> >> > > >>>>>
>>>>> >> > > >>>>> Thanks
>>>>> >> > > >>>>> Regards
>>>>> >> > > >>>>> Philippe
>>>>> >> > > >>>>>
>>>>> >> > > >>>>> On Sunday, March 12, 2017, Philippe Mouawad <
>>>>> >> > > >> philippe.moua...@gmail.com <javascript:;>>
>>>>> >> > > >>>>> wrote:
>>>>> >> > > >>>>>
>>>>> >> > > >>>>>> Hello,
>>>>> >> > > >>>>>> I've filled New and Noteworthy section, feel free to 
>>>>> >> > > >>>>>> improve.
>>>>> >> > > >>>>>> I've also documented migration to new logging.
>>>>> >> > > >>>>>>
>>>>> >> > > >>>>>> I think we can now release the 3.2 except for this bug which
>>>>> >> > exists
>>>>> >> > > >>>> since
>>>>> >> 

Re: Release a 3.2

[Woonsan Ko]

;>> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
>>>> >> > > >>
>>>> >> > > >> Andrey Pokhilko
>>>> >> > > >>
>>>> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
>>>> >> > > >>> Hello Andrey,
>>>> >> > > >>> Thanks for your tests.
>>>> >> > > >>> We're waiting for the Bugzilla, is it the issue mentioned by
>>>> >> somebody
>>>> >> > > on
>>>> >> > > >>> mailing list about a constant for Scripting languages ?
>>>> >> > > >>>
>>>> >> > > >>> Thanks
>>>> >> > > >>> Regards
>>>> >> > > >>>
>>>> >> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru
>>>> <javascript:;>>
>>>> >> wrote:
>>>> >> > > >>>
>>>> >> > > >>>> Hi,
>>>> >> > > >>>>
>>>> >> > > >>>> From plugins side, we've made check in BlazeMeter and found a
>>>> >> number
>>>> >> > > of
>>>> >> > > >>>> issues, mainly because of deleted methods and fields. We have
>>>> >> fixed
>>>> >> > > some
>>>> >> > > >>>> of them, but one is specifically breaking WebDriver sampler.
>>>> We're
>>>> >> > > going
>>>> >> > > >>>> to file bugzilla on it.
>>>> >> > > >>>>
>>>> >> > > >>>> IMO it's not good to release without fixing this, since it will
>>>> >> > break
>>>> >> > > >>>> everyone who uses WebDriver Sampler.
>>>> >> > > >>>>
>>>> >> > > >>>> Andrey Pokhilko
>>>> >> > > >>>>
>>>> >> > > >>>> On 16.03.2017 15:32, Philippe Mouawad wrote:
>>>> >> > > >>>>> Hello,
>>>> >> > > >>>>> Any feedback on patch ?
>>>> >> > > >>>>> Shall we proceed with release without fixing it ?
>>>> >> > > >>>>> Is there any other remaining work ?
>>>> >> > > >>>>>
>>>> >> > > >>>>> Thanks
>>>> >> > > >>>>> Regards
>>>> >> > > >>>>> Philippe
>>>> >> > > >>>>>
>>>> >> > > >>>>> On Sunday, March 12, 2017, Philippe Mouawad <
>>>> >> > > >> philippe.moua...@gmail.com <javascript:;>>
>>>> >> > > >>>>> wrote:
>>>> >> > > >>>>>
>>>> >> > > >>>>>> Hello,
>>>> >> > > >>>>>> I've filled New and Noteworthy section, feel free to improve.
>>>> >> > > >>>>>> I've also documented migration to new logging.
>>>> >> > > >>>>>>
>>>> >> > > >>>>>> I think we can now release the 3.2 except for this bug which
>>>> >> > exists
>>>> >> > > >>>> since
>>>> >> > > >>>>>> many versions, I've attached a patch for review:
>>>> >> > > >>>>>> - https://bz.apache.org/bugzilla/show_bug.cgi?id=60830
>>>> >> > > >>>>>>
>>>> >> > > >>>>>> Regards
>>>> >> > > >>>>>>
>>>> >> > > >>>>>> On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
>>>> >> > > >>>> ra0...@gmail.com <javascript:;>
>>>> >> > > >>>>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com
>>>> <javascript:;>');>> wrote:
>>>> >> > > >>>>>>
>>>> >> > > >>

Re: Release a 3.2

[Antonio Gomes Rodrigues]

PM, Antonio Gomes Rodrigues <
> > >> >>> >> >> ra0...@gmail.com <javascript:;>>
> > >> >>> >> >> wrote:
> > >> >>> >> >>
> > >> >>> >> >> > Hi,
> > >> >>> >> >> >
> > >> >>> >> >> > I have updated jmeter_accesslog_sampler_step_by_step
> > document
> > >> >>> like I
> > >> >>> >> >> have
> > >> >>> >> >> > said previously
> > >> >>> >> >> >
> > >> >>> >> >> > Antonio
> > >> >>> >> >> >
> > >> >>> >> >> > 2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru
> > >> >>> <javascript:;>
> > >> >>> >> >:
> > >> >>> >> >> >
> > >> >>> >> >> > > We have fixed them and released plugin updates. For the
> > >> >>> record, it
> > >> >>> >> >> were:
> > >> >>> >> >> > >
> > >> >>> >> >> > >   * OAuth Sampler broken - we decided to deprecate it
> > >> >>> >> >> > >   * JMX Check tool were failing on call to removed
> > >> >>> >> >> > > "org.apache.jmeter.save.SaveService.loadTree(
> > >> InputStream
> > >> >>> >> >> > > inputStream)", we've released update with other
> method
> > >> used
> > >> >>> >> >> > >   * Synthesis report were failing on call to modified
> > >> >>> >> >> > > "org.apache.jmeter.save.
> CSVSaveService#saveCSVStats(
> > >> >>> >> >> > java.util.List,
> > >> >>> >> >> > > java.io.FileWriter, java.lang.String[])", we've
> > released
> > >> >>> update
> > >> >>> >> >> that
> > >> >>> >> >> > > uses different method
> > >> >>> >> >> > >   * BlazeMeter Debugger plugin fails due to changes to
> > >> >>> LoggerPanel
> > >> >>> >> and
> > >> >>> >> >> > > several other changes around logging, we have no
> good
> > >> >>> solution
> > >> >>> >> for
> > >> >>> >> >> > > now, that will work on both JMeter 3.1 and 3.2. We
> > need
> > >> >>> more
> > >> >>> >> time
> > >> >>> >> >> to
> > >> >>> >> >> > > work on it and we don't consider it as release
> > blocker.
> > >> >>> >> >> > >
> > >> >>> >> >> > > Andrey Pokhilko
> > >> >>> >> >> > >
> > >> >>> >> >> > > On 16.03.2017 16:03, Philippe Mouawad wrote:
> > >> >>> >> >> > > > What are the other "number of issues " ?
> > >> >>> >> >> > > > Thanks
> > >> >>> >> >> > > >
> > >> >>> >> >> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <
> > >> a...@ya.ru
> > >> >>> >> <javascript:;>> wrote:
> > >> >>> >> >> > > >
> > >> >>> >> >> > > >> Hi,
> > >> >>> >> >> > > >>
> > >> >>> >> >> > > >> Yes, it's that message. The bugzilla is here:
> > >> >>> >> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
> > >> >>> >> >> > > >>
> > >> >>> >> >> > > >> Andrey Pokhilko
> > >> >>> >> >> > > >>
> > >> >>> >> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
> > >> >>> >> >> > > >>> Hello Andrey

Re: Release a 3.2

[Antonio Gomes Rodrigues]

gt;> InputStream
>> >>> >> >> > > inputStream)", we've released update with other method
>> used
>> >>> >> >> > >   * Synthesis report were failing on call to modified
>> >>> >> >> > > "org.apache.jmeter.save.CSVSaveService#saveCSVStats(
>> >>> >> >> > java.util.List,
>> >>> >> >> > > java.io.FileWriter, java.lang.String[])", we've released
>> >>> update
>> >>> >> >> that
>> >>> >> >> > > uses different method
>> >>> >> >> > >   * BlazeMeter Debugger plugin fails due to changes to
>> >>> LoggerPanel
>> >>> >> and
>> >>> >> >> > > several other changes around logging, we have no good
>> >>> solution
>> >>> >> for
>> >>> >> >> > > now, that will work on both JMeter 3.1 and 3.2. We need
>> >>> more
>> >>> >> time
>> >>> >> >> to
>> >>> >> >> > > work on it and we don't consider it as release blocker.
>> >>> >> >> > >
>> >>> >> >> > > Andrey Pokhilko
>> >>> >> >> > >
>> >>> >> >> > > On 16.03.2017 16:03, Philippe Mouawad wrote:
>> >>> >> >> > > > What are the other "number of issues " ?
>> >>> >> >> > > > Thanks
>> >>> >> >> > > >
>> >>> >> >> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <
>> a...@ya.ru
>> >>> >> <javascript:;>> wrote:
>> >>> >> >> > > >
>> >>> >> >> > > >> Hi,
>> >>> >> >> > > >>
>> >>> >> >> > > >> Yes, it's that message. The bugzilla is here:
>> >>> >> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
>> >>> >> >> > > >>
>> >>> >> >> > > >> Andrey Pokhilko
>> >>> >> >> > > >>
>> >>> >> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
>> >>> >> >> > > >>> Hello Andrey,
>> >>> >> >> > > >>> Thanks for your tests.
>> >>> >> >> > > >>> We're waiting for the Bugzilla, is it the issue
>> mentioned
>> >>> by
>> >>> >> >> somebody
>> >>> >> >> > > on
>> >>> >> >> > > >>> mailing list about a constant for Scripting languages ?
>> >>> >> >> > > >>>
>> >>> >> >> > > >>> Thanks
>> >>> >> >> > > >>> Regards
>> >>> >> >> > > >>>
>> >>> >> >> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <
>> >>> a...@ya.ru
>> >>> >> <javascript:;>>
>> >>> >> >> wrote:
>> >>> >> >> > > >>>
>> >>> >> >> > > >>>> Hi,
>> >>> >> >> > > >>>>
>> >>> >> >> > > >>>> From plugins side, we've made check in BlazeMeter and
>> >>> found a
>> >>> >> >> number
>> >>> >> >> > > of
>> >>> >> >> > > >>>> issues, mainly because of deleted methods and fields.
>> We
>> >>> have
>> >>> >> >> fixed
>> >>> >> >> > > some
>> >>> >> >> > > >>>> of them, but one is specifically breaking WebDriver
>> >>> sampler.
>> >>> >> We're
>> >>> >> >> > > going
>> >>> >> >> > > >>>> to file bugzilla on it.
>> >>> >> >> > > >>>>
>> >>> >> >> > > >>>> IMO it's not good to release without fixing this, since
>>

Re: Release a 3.2

[Antonio Gomes Rodrigues]

>> >> >> > > uses different method
> >>> >> >> > >   * BlazeMeter Debugger plugin fails due to changes to
> >>> LoggerPanel
> >>> >> and
> >>> >> >> > > several other changes around logging, we have no good
> >>> solution
> >>> >> for
> >>> >> >> > > now, that will work on both JMeter 3.1 and 3.2. We need
> >>> more
> >>> >> time
> >>> >> >> to
> >>> >> >> > > work on it and we don't consider it as release blocker.
> >>> >> >> > >
> >>> >> >> > > Andrey Pokhilko
> >>> >> >> > >
> >>> >> >> > > On 16.03.2017 16:03, Philippe Mouawad wrote:
> >>> >> >> > > > What are the other "number of issues " ?
> >>> >> >> > > > Thanks
> >>> >> >> > > >
> >>> >> >> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <
> a...@ya.ru
> >>> >> <javascript:;>> wrote:
> >>> >> >> > > >
> >>> >> >> > > >> Hi,
> >>> >> >> > > >>
> >>> >> >> > > >> Yes, it's that message. The bugzilla is here:
> >>> >> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
> >>> >> >> > > >>
> >>> >> >> > > >> Andrey Pokhilko
> >>> >> >> > > >>
> >>> >> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
> >>> >> >> > > >>> Hello Andrey,
> >>> >> >> > > >>> Thanks for your tests.
> >>> >> >> > > >>> We're waiting for the Bugzilla, is it the issue mentioned
> >>> by
> >>> >> >> somebody
> >>> >> >> > > on
> >>> >> >> > > >>> mailing list about a constant for Scripting languages ?
> >>> >> >> > > >>>
> >>> >> >> > > >>> Thanks
> >>> >> >> > > >>> Regards
> >>> >> >> > > >>>
> >>> >> >> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <
> >>> a...@ya.ru
> >>> >> <javascript:;>>
> >>> >> >> wrote:
> >>> >> >> > > >>>
> >>> >> >> > > >>>> Hi,
> >>> >> >> > > >>>>
> >>> >> >> > > >>>> From plugins side, we've made check in BlazeMeter and
> >>> found a
> >>> >> >> number
> >>> >> >> > > of
> >>> >> >> > > >>>> issues, mainly because of deleted methods and fields. We
> >>> have
> >>> >> >> fixed
> >>> >> >> > > some
> >>> >> >> > > >>>> of them, but one is specifically breaking WebDriver
> >>> sampler.
> >>> >> We're
> >>> >> >> > > going
> >>> >> >> > > >>>> to file bugzilla on it.
> >>> >> >> > > >>>>
> >>> >> >> > > >>>> IMO it's not good to release without fixing this, since
> >>> it will
> >>> >> >> > break
> >>> >> >> > > >>>> everyone who uses WebDriver Sampler.
> >>> >> >> > > >>>>
> >>> >> >> > > >>>> Andrey Pokhilko
> >>> >> >> > > >>>>
> >>> >> >> > > >>>> On 16.03.2017 15:32, Philippe Mouawad wrote:
> >>> >> >> > > >>>>> Hello,
> >>> >> >> > > >>>>> Any feedback on patch ?
> >>> >> >> > > >>>>> Shall we proceed with release without fixing it ?
> >>> >> >> > > >>>>> Is there any other remaining work ?
> >>> >> &

Re: Release a 3.2

[Philippe Mouawad]

gt; >> >> > > Andrey Pokhilko
>>> >> >> > >
>>> >> >> > > On 16.03.2017 16:03, Philippe Mouawad wrote:
>>> >> >> > > > What are the other "number of issues " ?
>>> >> >> > > > Thanks
>>> >> >> > > >
>>> >> >> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru
>>> >> <javascript:;>> wrote:
>>> >> >> > > >
>>> >> >> > > >> Hi,
>>> >> >> > > >>
>>> >> >> > > >> Yes, it's that message. The bugzilla is here:
>>> >> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
>>> >> >> > > >>
>>> >> >> > > >> Andrey Pokhilko
>>> >> >> > > >>
>>> >> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
>>> >> >> > > >>> Hello Andrey,
>>> >> >> > > >>> Thanks for your tests.
>>> >> >> > > >>> We're waiting for the Bugzilla, is it the issue mentioned
>>> by
>>> >> >> somebody
>>> >> >> > > on
>>> >> >> > > >>> mailing list about a constant for Scripting languages ?
>>> >> >> > > >>>
>>> >> >> > > >>> Thanks
>>> >> >> > > >>> Regards
>>> >> >> > > >>>
>>> >> >> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <
>>> a...@ya.ru
>>> >> <javascript:;>>
>>> >> >> wrote:
>>> >> >> > > >>>
>>> >> >> > > >>>> Hi,
>>> >> >> > > >>>>
>>> >> >> > > >>>> From plugins side, we've made check in BlazeMeter and
>>> found a
>>> >> >> number
>>> >> >> > > of
>>> >> >> > > >>>> issues, mainly because of deleted methods and fields. We
>>> have
>>> >> >> fixed
>>> >> >> > > some
>>> >> >> > > >>>> of them, but one is specifically breaking WebDriver
>>> sampler.
>>> >> We're
>>> >> >> > > going
>>> >> >> > > >>>> to file bugzilla on it.
>>> >> >> > > >>>>
>>> >> >> > > >>>> IMO it's not good to release without fixing this, since
>>> it will
>>> >> >> > break
>>> >> >> > > >>>> everyone who uses WebDriver Sampler.
>>> >> >> > > >>>>
>>> >> >> > > >>>> Andrey Pokhilko
>>> >> >> > > >>>>
>>> >> >> > > >>>> On 16.03.2017 15:32, Philippe Mouawad wrote:
>>> >> >> > > >>>>> Hello,
>>> >> >> > > >>>>> Any feedback on patch ?
>>> >> >> > > >>>>> Shall we proceed with release without fixing it ?
>>> >> >> > > >>>>> Is there any other remaining work ?
>>> >> >> > > >>>>>
>>> >> >> > > >>>>> Thanks
>>> >> >> > > >>>>> Regards
>>> >> >> > > >>>>> Philippe
>>> >> >> > > >>>>>
>>> >> >> > > >>>>> On Sunday, March 12, 2017, Philippe Mouawad <
>>> >> >> > > >> philippe.moua...@gmail.com <javascript:;>>
>>> >> >> > > >>>>> wrote:
>>> >> >> > > >>>>>
>>> >> >> > > >>>>>> Hello,
>>> >> >> > > >>>>>> I've filled New and Noteworthy section, feel free to
>>> improve.
>>> >> >> > > >>>>>> I've also documented migration to new logging.
>>> >> >> > > >>>

Re: Release a 3.2

[sebb]

On 20 March 2017 at 22:57, Philippe Mouawad <philippe.moua...@gmail.com> wrote:
> On Monday, March 20, 2017, sebb <seb...@gmail.com> wrote:
>
>> I know I keep going on about this, but the logging documentation still
>> needs some work.
>>
>> The logging level names have changed.
>> Users need to be told what the mapping is from old name to new name.
>>
>> cf comments on r1786590
>
> Work has been done since that time.
> Please point to missing information.

Where are the logging levels documented?
I had a quick look and could not find them.

>
>>
>>
>> On 20 March 2017 at 22:26, Antonio Gomes Rodrigues <ra0...@gmail.com
>> <javascript:;>> wrote:
>> > +1
>> >
>> > Antonio
>> >
>> > 2017-03-20 21:49 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com
>> <javascript:;>>:
>> >
>> >> Hello,
>> >> AFAIU, there are no more pending points for a release.
>> >>
>> >> Am I wrong ?
>> >> If not, could be start a release ?
>> >> Thanks
>> >> Regards
>> >>
>> >>
>> >> On Thu, Mar 16, 2017 at 11:43 PM, Antonio Gomes Rodrigues <
>> >> ra0...@gmail.com <javascript:;>>
>> >> wrote:
>> >>
>> >> > Hi,
>> >> >
>> >> > I have updated jmeter_accesslog_sampler_step_by_step document like I
>> >> have
>> >> > said previously
>> >> >
>> >> > Antonio
>> >> >
>> >> > 2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru <javascript:;>
>> >:
>> >> >
>> >> > > We have fixed them and released plugin updates. For the record, it
>> >> were:
>> >> > >
>> >> > >   * OAuth Sampler broken - we decided to deprecate it
>> >> > >   * JMX Check tool were failing on call to removed
>> >> > > "org.apache.jmeter.save.SaveService.loadTree( InputStream
>> >> > > inputStream)", we've released update with other method used
>> >> > >   * Synthesis report were failing on call to modified
>> >> > > "org.apache.jmeter.save.CSVSaveService#saveCSVStats(
>> >> > java.util.List,
>> >> > > java.io.FileWriter, java.lang.String[])", we've released update
>> >> that
>> >> > > uses different method
>> >> > >   * BlazeMeter Debugger plugin fails due to changes to LoggerPanel
>> and
>> >> > > several other changes around logging, we have no good solution
>> for
>> >> > > now, that will work on both JMeter 3.1 and 3.2. We need more
>> time
>> >> to
>> >> > > work on it and we don't consider it as release blocker.
>> >> > >
>> >> > > Andrey Pokhilko
>> >> > >
>> >> > > On 16.03.2017 16:03, Philippe Mouawad wrote:
>> >> > > > What are the other "number of issues " ?
>> >> > > > Thanks
>> >> > > >
>> >> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru
>> <javascript:;>> wrote:
>> >> > > >
>> >> > > >> Hi,
>> >> > > >>
>> >> > > >> Yes, it's that message. The bugzilla is here:
>> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
>> >> > > >>
>> >> > > >> Andrey Pokhilko
>> >> > > >>
>> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
>> >> > > >>> Hello Andrey,
>> >> > > >>> Thanks for your tests.
>> >> > > >>> We're waiting for the Bugzilla, is it the issue mentioned by
>> >> somebody
>> >> > > on
>> >> > > >>> mailing list about a constant for Scripting languages ?
>> >> > > >>>
>> >> > > >>> Thanks
>> >> > > >>> Regards
>> >> > > >>>
>> >> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru
>> <javascript:;>>
>> >> wrote:
>> >> > > >>>
>> >> > > >>>> Hi,
>> >> > > >>>&g

Re: Release a 3.2

[Philippe Mouawad]

On Monday, March 20, 2017, sebb <seb...@gmail.com> wrote:

> I know I keep going on about this, but the logging documentation still
> needs some work.
>
> The logging level names have changed.
> Users need to be told what the mapping is from old name to new name.
>
> cf comments on r1786590

Work has been done since that time.
Please point to missing information.


>
>
> On 20 March 2017 at 22:26, Antonio Gomes Rodrigues <ra0...@gmail.com
> <javascript:;>> wrote:
> > +1
> >
> > Antonio
> >
> > 2017-03-20 21:49 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com
> <javascript:;>>:
> >
> >> Hello,
> >> AFAIU, there are no more pending points for a release.
> >>
> >> Am I wrong ?
> >> If not, could be start a release ?
> >> Thanks
> >> Regards
> >>
> >>
> >> On Thu, Mar 16, 2017 at 11:43 PM, Antonio Gomes Rodrigues <
> >> ra0...@gmail.com <javascript:;>>
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > I have updated jmeter_accesslog_sampler_step_by_step document like I
> >> have
> >> > said previously
> >> >
> >> > Antonio
> >> >
> >> > 2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru <javascript:;>
> >:
> >> >
> >> > > We have fixed them and released plugin updates. For the record, it
> >> were:
> >> > >
> >> > >   * OAuth Sampler broken - we decided to deprecate it
> >> > >   * JMX Check tool were failing on call to removed
> >> > > "org.apache.jmeter.save.SaveService.loadTree( InputStream
> >> > > inputStream)", we've released update with other method used
> >> > >   * Synthesis report were failing on call to modified
> >> > > "org.apache.jmeter.save.CSVSaveService#saveCSVStats(
> >> > java.util.List,
> >> > > java.io.FileWriter, java.lang.String[])", we've released update
> >> that
> >> > > uses different method
> >> > >   * BlazeMeter Debugger plugin fails due to changes to LoggerPanel
> and
> >> > > several other changes around logging, we have no good solution
> for
> >> > > now, that will work on both JMeter 3.1 and 3.2. We need more
> time
> >> to
> >> > > work on it and we don't consider it as release blocker.
> >> > >
> >> > > Andrey Pokhilko
> >> > >
> >> > > On 16.03.2017 16:03, Philippe Mouawad wrote:
> >> > > > What are the other "number of issues " ?
> >> > > > Thanks
> >> > > >
> >> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru
> <javascript:;>> wrote:
> >> > > >
> >> > > >> Hi,
> >> > > >>
> >> > > >> Yes, it's that message. The bugzilla is here:
> >> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
> >> > > >>
> >> > > >> Andrey Pokhilko
> >> > > >>
> >> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
> >> > > >>> Hello Andrey,
> >> > > >>> Thanks for your tests.
> >> > > >>> We're waiting for the Bugzilla, is it the issue mentioned by
> >> somebody
> >> > > on
> >> > > >>> mailing list about a constant for Scripting languages ?
> >> > > >>>
> >> > > >>> Thanks
> >> > > >>> Regards
> >> > > >>>
> >> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru
> <javascript:;>>
> >> wrote:
> >> > > >>>
> >> > > >>>> Hi,
> >> > > >>>>
> >> > > >>>> From plugins side, we've made check in BlazeMeter and found a
> >> number
> >> > > of
> >> > > >>>> issues, mainly because of deleted methods and fields. We have
> >> fixed
> >> > > some
> >> > > >>>> of them, but one is specifically breaking WebDriver sampler.
> We're
> >> > > going
> >> > > >>>> to file bugzilla on it.
> >> > > >>>>
> >> > > >>>&

Re: Release a 3.2

[Antonio Gomes Rodrigues]

+1

Antonio

2017-03-20 21:49 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:

> Hello,
> AFAIU, there are no more pending points for a release.
>
> Am I wrong ?
> If not, could be start a release ?
> Thanks
> Regards
>
>
> On Thu, Mar 16, 2017 at 11:43 PM, Antonio Gomes Rodrigues <
> ra0...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I have updated jmeter_accesslog_sampler_step_by_step document like I
> have
> > said previously
> >
> > Antonio
> >
> > 2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru>:
> >
> > > We have fixed them and released plugin updates. For the record, it
> were:
> > >
> > >   * OAuth Sampler broken - we decided to deprecate it
> > >   * JMX Check tool were failing on call to removed
> > > "org.apache.jmeter.save.SaveService.loadTree( InputStream
> > > inputStream)", we've released update with other method used
> > >   * Synthesis report were failing on call to modified
> > > "org.apache.jmeter.save.CSVSaveService#saveCSVStats(
> > java.util.List,
> > > java.io.FileWriter, java.lang.String[])", we've released update
> that
> > > uses different method
> > >   * BlazeMeter Debugger plugin fails due to changes to LoggerPanel and
> > > several other changes around logging, we have no good solution for
> > > now, that will work on both JMeter 3.1 and 3.2. We need more time
> to
> > > work on it and we don't consider it as release blocker.
> > >
> > > Andrey Pokhilko
> > >
> > > On 16.03.2017 16:03, Philippe Mouawad wrote:
> > > > What are the other "number of issues " ?
> > > > Thanks
> > > >
> > > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> Yes, it's that message. The bugzilla is here:
> > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
> > > >>
> > > >> Andrey Pokhilko
> > > >>
> > > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
> > > >>> Hello Andrey,
> > > >>> Thanks for your tests.
> > > >>> We're waiting for the Bugzilla, is it the issue mentioned by
> somebody
> > > on
> > > >>> mailing list about a constant for Scripting languages ?
> > > >>>
> > > >>> Thanks
> > > >>> Regards
> > > >>>
> > > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru>
> wrote:
> > > >>>
> > > >>>> Hi,
> > > >>>>
> > > >>>> From plugins side, we've made check in BlazeMeter and found a
> number
> > > of
> > > >>>> issues, mainly because of deleted methods and fields. We have
> fixed
> > > some
> > > >>>> of them, but one is specifically breaking WebDriver sampler. We're
> > > going
> > > >>>> to file bugzilla on it.
> > > >>>>
> > > >>>> IMO it's not good to release without fixing this, since it will
> > break
> > > >>>> everyone who uses WebDriver Sampler.
> > > >>>>
> > > >>>> Andrey Pokhilko
> > > >>>>
> > > >>>> On 16.03.2017 15:32, Philippe Mouawad wrote:
> > > >>>>> Hello,
> > > >>>>> Any feedback on patch ?
> > > >>>>> Shall we proceed with release without fixing it ?
> > > >>>>> Is there any other remaining work ?
> > > >>>>>
> > > >>>>> Thanks
> > > >>>>> Regards
> > > >>>>> Philippe
> > > >>>>>
> > > >>>>> On Sunday, March 12, 2017, Philippe Mouawad <
> > > >> philippe.moua...@gmail.com>
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> Hello,
> > > >>>>>> I've filled New and Noteworthy section, feel free to improve.
> > > >>>>>> I've also documented migration to new logging.
> > > >>>>>>
> > > >>>>>> I think we can now release the 3.2 except for this bug which
> > exists
> > > >>>> since
> > > >

Re: Release a 3.2

[Philippe Mouawad]

Hello,
AFAIU, there are no more pending points for a release.

Am I wrong ?
If not, could be start a release ?
Thanks
Regards


On Thu, Mar 16, 2017 at 11:43 PM, Antonio Gomes Rodrigues <ra0...@gmail.com>
wrote:

> Hi,
>
> I have updated jmeter_accesslog_sampler_step_by_step document like I have
> said previously
>
> Antonio
>
> 2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru>:
>
> > We have fixed them and released plugin updates. For the record, it were:
> >
> >   * OAuth Sampler broken - we decided to deprecate it
> >   * JMX Check tool were failing on call to removed
> > "org.apache.jmeter.save.SaveService.loadTree( InputStream
> > inputStream)", we've released update with other method used
> >   * Synthesis report were failing on call to modified
> > "org.apache.jmeter.save.CSVSaveService#saveCSVStats(
> java.util.List,
> > java.io.FileWriter, java.lang.String[])", we've released update that
> > uses different method
> >   * BlazeMeter Debugger plugin fails due to changes to LoggerPanel and
> > several other changes around logging, we have no good solution for
> > now, that will work on both JMeter 3.1 and 3.2. We need more time to
> > work on it and we don't consider it as release blocker.
> >
> > Andrey Pokhilko
> >
> > On 16.03.2017 16:03, Philippe Mouawad wrote:
> > > What are the other "number of issues " ?
> > > Thanks
> > >
> > > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru> wrote:
> > >
> > >> Hi,
> > >>
> > >> Yes, it's that message. The bugzilla is here:
> > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
> > >>
> > >> Andrey Pokhilko
> > >>
> > >> On 16.03.2017 16:01, Philippe Mouawad wrote:
> > >>> Hello Andrey,
> > >>> Thanks for your tests.
> > >>> We're waiting for the Bugzilla, is it the issue mentioned by somebody
> > on
> > >>> mailing list about a constant for Scripting languages ?
> > >>>
> > >>> Thanks
> > >>> Regards
> > >>>
> > >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru> wrote:
> > >>>
> > >>>> Hi,
> > >>>>
> > >>>> From plugins side, we've made check in BlazeMeter and found a number
> > of
> > >>>> issues, mainly because of deleted methods and fields. We have fixed
> > some
> > >>>> of them, but one is specifically breaking WebDriver sampler. We're
> > going
> > >>>> to file bugzilla on it.
> > >>>>
> > >>>> IMO it's not good to release without fixing this, since it will
> break
> > >>>> everyone who uses WebDriver Sampler.
> > >>>>
> > >>>> Andrey Pokhilko
> > >>>>
> > >>>> On 16.03.2017 15:32, Philippe Mouawad wrote:
> > >>>>> Hello,
> > >>>>> Any feedback on patch ?
> > >>>>> Shall we proceed with release without fixing it ?
> > >>>>> Is there any other remaining work ?
> > >>>>>
> > >>>>> Thanks
> > >>>>> Regards
> > >>>>> Philippe
> > >>>>>
> > >>>>> On Sunday, March 12, 2017, Philippe Mouawad <
> > >> philippe.moua...@gmail.com>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> Hello,
> > >>>>>> I've filled New and Noteworthy section, feel free to improve.
> > >>>>>> I've also documented migration to new logging.
> > >>>>>>
> > >>>>>> I think we can now release the 3.2 except for this bug which
> exists
> > >>>> since
> > >>>>>> many versions, I've attached a patch for review:
> > >>>>>> - https://bz.apache.org/bugzilla/show_bug.cgi?id=60830
> > >>>>>>
> > >>>>>> Regards
> > >>>>>>
> > >>>>>> On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
> > >>>> ra0...@gmail.com
> > >>>>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>> wrote:
> > >>>>>>
> > >>>>>>> Hi,
> > >>>>>>>
> &

Re: Release a 3.2

[Antonio Gomes Rodrigues]

Hi,

I have updated jmeter_accesslog_sampler_step_by_step document like I have
said previously

Antonio

2017-03-16 14:25 GMT+01:00 Andrey Pokhilko <a...@ya.ru>:

> We have fixed them and released plugin updates. For the record, it were:
>
>   * OAuth Sampler broken - we decided to deprecate it
>   * JMX Check tool were failing on call to removed
> "org.apache.jmeter.save.SaveService.loadTree( InputStream
> inputStream)", we've released update with other method used
>   * Synthesis report were failing on call to modified
> "org.apache.jmeter.save.CSVSaveService#saveCSVStats(java.util.List,
> java.io.FileWriter, java.lang.String[])", we've released update that
> uses different method
>   * BlazeMeter Debugger plugin fails due to changes to LoggerPanel and
> several other changes around logging, we have no good solution for
> now, that will work on both JMeter 3.1 and 3.2. We need more time to
> work on it and we don't consider it as release blocker.
>
> Andrey Pokhilko
>
> On 16.03.2017 16:03, Philippe Mouawad wrote:
> > What are the other "number of issues " ?
> > Thanks
> >
> > On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru> wrote:
> >
> >> Hi,
> >>
> >> Yes, it's that message. The bugzilla is here:
> >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
> >>
> >> Andrey Pokhilko
> >>
> >> On 16.03.2017 16:01, Philippe Mouawad wrote:
> >>> Hello Andrey,
> >>> Thanks for your tests.
> >>> We're waiting for the Bugzilla, is it the issue mentioned by somebody
> on
> >>> mailing list about a constant for Scripting languages ?
> >>>
> >>> Thanks
> >>> Regards
> >>>
> >>> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> From plugins side, we've made check in BlazeMeter and found a number
> of
> >>>> issues, mainly because of deleted methods and fields. We have fixed
> some
> >>>> of them, but one is specifically breaking WebDriver sampler. We're
> going
> >>>> to file bugzilla on it.
> >>>>
> >>>> IMO it's not good to release without fixing this, since it will break
> >>>> everyone who uses WebDriver Sampler.
> >>>>
> >>>> Andrey Pokhilko
> >>>>
> >>>> On 16.03.2017 15:32, Philippe Mouawad wrote:
> >>>>> Hello,
> >>>>> Any feedback on patch ?
> >>>>> Shall we proceed with release without fixing it ?
> >>>>> Is there any other remaining work ?
> >>>>>
> >>>>> Thanks
> >>>>> Regards
> >>>>> Philippe
> >>>>>
> >>>>> On Sunday, March 12, 2017, Philippe Mouawad <
> >> philippe.moua...@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Hello,
> >>>>>> I've filled New and Noteworthy section, feel free to improve.
> >>>>>> I've also documented migration to new logging.
> >>>>>>
> >>>>>> I think we can now release the 3.2 except for this bug which exists
> >>>> since
> >>>>>> many versions, I've attached a patch for review:
> >>>>>> - https://bz.apache.org/bugzilla/show_bug.cgi?id=60830
> >>>>>>
> >>>>>> Regards
> >>>>>>
> >>>>>> On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
> >>>> ra0...@gmail.com
> >>>>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>> wrote:
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> Modifications in the PR done
> >>>>>>>
> >>>>>>> Antonio
> >>>>>>>
> >>>>>>> 2017-03-06 15:51 GMT+01:00 Antonio Gomes Rodrigues <
> ra0...@gmail.com
> >>>>>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>>:
> >>>>>>>
> >>>>>>>> Hi Philippe
> >>>>>>>>
> >>>>>>>> 2017-03-06 8:40 GMT+01:00 Philippe Mouawad <
> >>>> philippe.moua...@gmail.com
> >>>>>>> <javascript:_e(%7B%7D,'cvml'

Re: Release a 3.2

[Philippe Mouawad]

What are the other "number of issues " ?
Thanks

On Thu, Mar 16, 2017 at 2:02 PM, Andrey Pokhilko <a...@ya.ru> wrote:

> Hi,
>
> Yes, it's that message. The bugzilla is here:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=60874
>
> Andrey Pokhilko
>
> On 16.03.2017 16:01, Philippe Mouawad wrote:
> > Hello Andrey,
> > Thanks for your tests.
> > We're waiting for the Bugzilla, is it the issue mentioned by somebody on
> > mailing list about a constant for Scripting languages ?
> >
> > Thanks
> > Regards
> >
> > On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru> wrote:
> >
> >> Hi,
> >>
> >> From plugins side, we've made check in BlazeMeter and found a number of
> >> issues, mainly because of deleted methods and fields. We have fixed some
> >> of them, but one is specifically breaking WebDriver sampler. We're going
> >> to file bugzilla on it.
> >>
> >> IMO it's not good to release without fixing this, since it will break
> >> everyone who uses WebDriver Sampler.
> >>
> >> Andrey Pokhilko
> >>
> >> On 16.03.2017 15:32, Philippe Mouawad wrote:
> >>> Hello,
> >>> Any feedback on patch ?
> >>> Shall we proceed with release without fixing it ?
> >>> Is there any other remaining work ?
> >>>
> >>> Thanks
> >>> Regards
> >>> Philippe
> >>>
> >>> On Sunday, March 12, 2017, Philippe Mouawad <
> philippe.moua...@gmail.com>
> >>> wrote:
> >>>
> >>>> Hello,
> >>>> I've filled New and Noteworthy section, feel free to improve.
> >>>> I've also documented migration to new logging.
> >>>>
> >>>> I think we can now release the 3.2 except for this bug which exists
> >> since
> >>>> many versions, I've attached a patch for review:
> >>>> - https://bz.apache.org/bugzilla/show_bug.cgi?id=60830
> >>>>
> >>>> Regards
> >>>>
> >>>> On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
> >> ra0...@gmail.com
> >>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> Modifications in the PR done
> >>>>>
> >>>>> Antonio
> >>>>>
> >>>>> 2017-03-06 15:51 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com
> >>>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>>:
> >>>>>
> >>>>>> Hi Philippe
> >>>>>>
> >>>>>> 2017-03-06 8:40 GMT+01:00 Philippe Mouawad <
> >> philippe.moua...@gmail.com
> >>>>> <javascript:_e(%7B%7D,'cvml','philippe.moua...@gmail.com');>>:
> >>>>>>> Hello Antonio,
> >>>>>>> I 've reviewed it rapidly:
> >>>>>>> - button at the bottom => In nightly build it is at top now and
> >> buttons
> >>>>>>> have changed
> >>>>>>>
> >>>>>> Ok, I will modify it
> >>>>>>
> >>>>>>
> >>>>>>> - With the gui, but it's not recommended to big load test => With
> the
> >>>>> gui,
> >>>>>>> but just during debug phase, use Non GUI for your load test.
> >>>>>>>
> >>>>>> Ok, I will modify it
> >>>>>>
> >>>>>>
> >>>>>>> I think you should mention that between Validation phase and Run
> >> phase
> >>>>>>> there is variabilization and Correlation phase.
> >>>>>>>
> >>>>>> Not added because it's not present in the original document
> >>>>>> I will mention it and add some tips
> >>>>>>
> >>>>>> Antonio
> >>>>>>
> >>>>>>> Thanks
> >>>>>>> Regards
> >>>>>>>
> >>>>>>> On Sun, Mar 5, 2017 at 7:10 PM, Antonio Gomes Rodrigues <
> >>>>> ra0...@gmail.com <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>&g

Re: Release a 3.2

[Andrey Pokhilko]

Hi,

Yes, it's that message. The bugzilla is here:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60874

Andrey Pokhilko

On 16.03.2017 16:01, Philippe Mouawad wrote:
> Hello Andrey,
> Thanks for your tests.
> We're waiting for the Bugzilla, is it the issue mentioned by somebody on
> mailing list about a constant for Scripting languages ?
>
> Thanks
> Regards
>
> On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru> wrote:
>
>> Hi,
>>
>> From plugins side, we've made check in BlazeMeter and found a number of
>> issues, mainly because of deleted methods and fields. We have fixed some
>> of them, but one is specifically breaking WebDriver sampler. We're going
>> to file bugzilla on it.
>>
>> IMO it's not good to release without fixing this, since it will break
>> everyone who uses WebDriver Sampler.
>>
>> Andrey Pokhilko
>>
>> On 16.03.2017 15:32, Philippe Mouawad wrote:
>>> Hello,
>>> Any feedback on patch ?
>>> Shall we proceed with release without fixing it ?
>>> Is there any other remaining work ?
>>>
>>> Thanks
>>> Regards
>>> Philippe
>>>
>>> On Sunday, March 12, 2017, Philippe Mouawad <philippe.moua...@gmail.com>
>>> wrote:
>>>
>>>> Hello,
>>>> I've filled New and Noteworthy section, feel free to improve.
>>>> I've also documented migration to new logging.
>>>>
>>>> I think we can now release the 3.2 except for this bug which exists
>> since
>>>> many versions, I've attached a patch for review:
>>>> - https://bz.apache.org/bugzilla/show_bug.cgi?id=60830
>>>>
>>>> Regards
>>>>
>>>> On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
>> ra0...@gmail.com
>>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Modifications in the PR done
>>>>>
>>>>> Antonio
>>>>>
>>>>> 2017-03-06 15:51 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com
>>>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>>:
>>>>>
>>>>>> Hi Philippe
>>>>>>
>>>>>> 2017-03-06 8:40 GMT+01:00 Philippe Mouawad <
>> philippe.moua...@gmail.com
>>>>> <javascript:_e(%7B%7D,'cvml','philippe.moua...@gmail.com');>>:
>>>>>>> Hello Antonio,
>>>>>>> I 've reviewed it rapidly:
>>>>>>> - button at the bottom => In nightly build it is at top now and
>> buttons
>>>>>>> have changed
>>>>>>>
>>>>>> Ok, I will modify it
>>>>>>
>>>>>>
>>>>>>> - With the gui, but it's not recommended to big load test => With the
>>>>> gui,
>>>>>>> but just during debug phase, use Non GUI for your load test.
>>>>>>>
>>>>>> Ok, I will modify it
>>>>>>
>>>>>>
>>>>>>> I think you should mention that between Validation phase and Run
>> phase
>>>>>>> there is variabilization and Correlation phase.
>>>>>>>
>>>>>> Not added because it's not present in the original document
>>>>>> I will mention it and add some tips
>>>>>>
>>>>>> Antonio
>>>>>>
>>>>>>> Thanks
>>>>>>> Regards
>>>>>>>
>>>>>>> On Sun, Mar 5, 2017 at 7:10 PM, Antonio Gomes Rodrigues <
>>>>> ra0...@gmail.com <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have modified jmeter proxy step by step document
>>>>>>>>
>>>>>>>> See my modifications in https://github.com/apache/jmeter/pull/279
>>>>>>>>
>>>>>>>> If it's ok, I will commit it in svn
>>>>>>>>
>>>>>>>> Antonio
>>>>>>>>
>>>>>>>> 2017-03-02 10:47 GMT+01:00 Maxime Chassagneux <
>>>>>>>> maxime.chassagn...@gmail.com
>>>>> <javascript:_e(%7B%7D,'cvml','maxime.chassagn...@gmail.com');>>
>>>>>>>> :
>

Re: Release a 3.2

[Philippe Mouawad]

Hello Andrey,
Thanks for your tests.
We're waiting for the Bugzilla, is it the issue mentioned by somebody on
mailing list about a constant for Scripting languages ?

Thanks
Regards

On Thu, Mar 16, 2017 at 1:43 PM, Andrey Pokhilko <a...@ya.ru> wrote:

> Hi,
>
> From plugins side, we've made check in BlazeMeter and found a number of
> issues, mainly because of deleted methods and fields. We have fixed some
> of them, but one is specifically breaking WebDriver sampler. We're going
> to file bugzilla on it.
>
> IMO it's not good to release without fixing this, since it will break
> everyone who uses WebDriver Sampler.
>
> Andrey Pokhilko
>
> On 16.03.2017 15:32, Philippe Mouawad wrote:
> > Hello,
> > Any feedback on patch ?
> > Shall we proceed with release without fixing it ?
> > Is there any other remaining work ?
> >
> > Thanks
> > Regards
> > Philippe
> >
> > On Sunday, March 12, 2017, Philippe Mouawad <philippe.moua...@gmail.com>
> > wrote:
> >
> >> Hello,
> >> I've filled New and Noteworthy section, feel free to improve.
> >> I've also documented migration to new logging.
> >>
> >> I think we can now release the 3.2 except for this bug which exists
> since
> >> many versions, I've attached a patch for review:
> >> - https://bz.apache.org/bugzilla/show_bug.cgi?id=60830
> >>
> >> Regards
> >>
> >> On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
> ra0...@gmail.com
> >> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>> wrote:
> >>
> >>> Hi,
> >>>
> >>> Modifications in the PR done
> >>>
> >>> Antonio
> >>>
> >>> 2017-03-06 15:51 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com
> >>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>>:
> >>>
> >>>> Hi Philippe
> >>>>
> >>>> 2017-03-06 8:40 GMT+01:00 Philippe Mouawad <
> philippe.moua...@gmail.com
> >>> <javascript:_e(%7B%7D,'cvml','philippe.moua...@gmail.com');>>:
> >>>>> Hello Antonio,
> >>>>> I 've reviewed it rapidly:
> >>>>> - button at the bottom => In nightly build it is at top now and
> buttons
> >>>>> have changed
> >>>>>
> >>>> Ok, I will modify it
> >>>>
> >>>>
> >>>>> - With the gui, but it's not recommended to big load test => With the
> >>> gui,
> >>>>> but just during debug phase, use Non GUI for your load test.
> >>>>>
> >>>> Ok, I will modify it
> >>>>
> >>>>
> >>>>> I think you should mention that between Validation phase and Run
> phase
> >>>>> there is variabilization and Correlation phase.
> >>>>>
> >>>> Not added because it's not present in the original document
> >>>> I will mention it and add some tips
> >>>>
> >>>> Antonio
> >>>>
> >>>>> Thanks
> >>>>> Regards
> >>>>>
> >>>>> On Sun, Mar 5, 2017 at 7:10 PM, Antonio Gomes Rodrigues <
> >>> ra0...@gmail.com <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> I have modified jmeter proxy step by step document
> >>>>>>
> >>>>>> See my modifications in https://github.com/apache/jmeter/pull/279
> >>>>>>
> >>>>>> If it's ok, I will commit it in svn
> >>>>>>
> >>>>>> Antonio
> >>>>>>
> >>>>>> 2017-03-02 10:47 GMT+01:00 Maxime Chassagneux <
> >>>>>> maxime.chassagn...@gmail.com
> >>> <javascript:_e(%7B%7D,'cvml','maxime.chassagn...@gmail.com');>>
> >>>>>> :
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> I have to update some screen + documentation for the JMS change
> >>> made
> >>>>> by
> >>>>>> me.
> >>>>>>> I will do it ASAP.
> >>>>>>>
> >>>>>>>
> >>>>>>> 2017-03-01 23:36 GMT+01:00 Antonio Gomes Rodrigues <
> >>>

Re: Release a 3.2

[Andrey Pokhilko]

Hi,

>From plugins side, we've made check in BlazeMeter and found a number of
issues, mainly because of deleted methods and fields. We have fixed some
of them, but one is specifically breaking WebDriver sampler. We're going
to file bugzilla on it.

IMO it's not good to release without fixing this, since it will break
everyone who uses WebDriver Sampler.

Andrey Pokhilko

On 16.03.2017 15:32, Philippe Mouawad wrote:
> Hello,
> Any feedback on patch ?
> Shall we proceed with release without fixing it ?
> Is there any other remaining work ?
>
> Thanks
> Regards
> Philippe
>
> On Sunday, March 12, 2017, Philippe Mouawad <philippe.moua...@gmail.com>
> wrote:
>
>> Hello,
>> I've filled New and Noteworthy section, feel free to improve.
>> I've also documented migration to new logging.
>>
>> I think we can now release the 3.2 except for this bug which exists since
>> many versions, I've attached a patch for review:
>> - https://bz.apache.org/bugzilla/show_bug.cgi?id=60830
>>
>> Regards
>>
>> On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <ra0...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>> wrote:
>>
>>> Hi,
>>>
>>> Modifications in the PR done
>>>
>>> Antonio
>>>
>>> 2017-03-06 15:51 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>>:
>>>
>>>> Hi Philippe
>>>>
>>>> 2017-03-06 8:40 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','philippe.moua...@gmail.com');>>:
>>>>> Hello Antonio,
>>>>> I 've reviewed it rapidly:
>>>>> - button at the bottom => In nightly build it is at top now and buttons
>>>>> have changed
>>>>>
>>>> Ok, I will modify it
>>>>
>>>>
>>>>> - With the gui, but it's not recommended to big load test => With the
>>> gui,
>>>>> but just during debug phase, use Non GUI for your load test.
>>>>>
>>>> Ok, I will modify it
>>>>
>>>>
>>>>> I think you should mention that between Validation phase and Run phase
>>>>> there is variabilization and Correlation phase.
>>>>>
>>>> Not added because it's not present in the original document
>>>> I will mention it and add some tips
>>>>
>>>> Antonio
>>>>
>>>>> Thanks
>>>>> Regards
>>>>>
>>>>> On Sun, Mar 5, 2017 at 7:10 PM, Antonio Gomes Rodrigues <
>>> ra0...@gmail.com <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have modified jmeter proxy step by step document
>>>>>>
>>>>>> See my modifications in https://github.com/apache/jmeter/pull/279
>>>>>>
>>>>>> If it's ok, I will commit it in svn
>>>>>>
>>>>>> Antonio
>>>>>>
>>>>>> 2017-03-02 10:47 GMT+01:00 Maxime Chassagneux <
>>>>>> maxime.chassagn...@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','maxime.chassagn...@gmail.com');>>
>>>>>> :
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have to update some screen + documentation for the JMS change
>>> made
>>>>> by
>>>>>> me.
>>>>>>> I will do it ASAP.
>>>>>>>
>>>>>>>
>>>>>>> 2017-03-01 23:36 GMT+01:00 Antonio Gomes Rodrigues <
>>> ra0...@gmail.com <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
>>>>>> :
>>>>>>>> 2017-03-01 23:03 GMT+01:00 Philippe Mouawad <
>>>>>> philippe.moua...@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','philippe.moua...@gmail.com');>
>>>>>>>> :
>>>>>>>>
>>>>>>>>> On Wed, Mar 1, 2017 at 10:59 PM, Antonio Gomes Rodrigues <
>>>>>>>> ra0...@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>

Re: Release a 3.2

[Philippe Mouawad]

Hello,
Any feedback on patch ?
Shall we proceed with release without fixing it ?
Is there any other remaining work ?

Thanks
Regards
Philippe

On Sunday, March 12, 2017, Philippe Mouawad <philippe.moua...@gmail.com>
wrote:

> Hello,
> I've filled New and Noteworthy section, feel free to improve.
> I've also documented migration to new logging.
>
> I think we can now release the 3.2 except for this bug which exists since
> many versions, I've attached a patch for review:
> - https://bz.apache.org/bugzilla/show_bug.cgi?id=60830
>
> Regards
>
> On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <ra0...@gmail.com
> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>> wrote:
>
>> Hi,
>>
>> Modifications in the PR done
>>
>> Antonio
>>
>> 2017-03-06 15:51 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>>:
>>
>> > Hi Philippe
>> >
>> > 2017-03-06 8:40 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','philippe.moua...@gmail.com');>>:
>> >
>> >> Hello Antonio,
>> >> I 've reviewed it rapidly:
>> >> - button at the bottom => In nightly build it is at top now and buttons
>> >> have changed
>> >>
>> > Ok, I will modify it
>> >
>> >
>> >> - With the gui, but it's not recommended to big load test => With the
>> gui,
>> >> but just during debug phase, use Non GUI for your load test.
>> >>
>> > Ok, I will modify it
>> >
>> >
>> >>
>> >> I think you should mention that between Validation phase and Run phase
>> >> there is variabilization and Correlation phase.
>> >>
>> > Not added because it's not present in the original document
>> > I will mention it and add some tips
>> >
>> > Antonio
>> >
>> >>
>> >> Thanks
>> >> Regards
>> >>
>> >> On Sun, Mar 5, 2017 at 7:10 PM, Antonio Gomes Rodrigues <
>> ra0...@gmail.com <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
>> >> >
>> >> wrote:
>> >>
>> >> > Hi,
>> >> >
>> >> > I have modified jmeter proxy step by step document
>> >> >
>> >> > See my modifications in https://github.com/apache/jmeter/pull/279
>> >> >
>> >> > If it's ok, I will commit it in svn
>> >> >
>> >> > Antonio
>> >> >
>> >> > 2017-03-02 10:47 GMT+01:00 Maxime Chassagneux <
>> >> > maxime.chassagn...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','maxime.chassagn...@gmail.com');>>
>> >> > :
>> >> >
>> >> > > Hi,
>> >> > >
>> >> > > I have to update some screen + documentation for the JMS change
>> made
>> >> by
>> >> > me.
>> >> > > I will do it ASAP.
>> >> > >
>> >> > >
>> >> > > 2017-03-01 23:36 GMT+01:00 Antonio Gomes Rodrigues <
>> ra0...@gmail.com <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
>> >> >:
>> >> > >
>> >> > > > 2017-03-01 23:03 GMT+01:00 Philippe Mouawad <
>> >> > philippe.moua...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','philippe.moua...@gmail.com');>
>> >> > > >:
>> >> > > >
>> >> > > > > On Wed, Mar 1, 2017 at 10:59 PM, Antonio Gomes Rodrigues <
>> >> > > > ra0...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','ra0...@gmail.com');>
>> >> > > > > >
>> >> > > > > wrote:
>> >> > > > >
>> >> > > > > > Hi,
>> >> > > > > >
>> >> > > > > > 1.
>> >> > > > > > One question, in jmeter_tutorial.html file we talk about a
>> >> > screenshot
>> >> > > > > which
>> >> > > > > > exit in pdf file but not in html file: "From the screen
>> >> capture, we
>> >> > > see
>> >> > > > > the
>> >> > > > > > following directories. "
>> >> > > > > >
>> >> > > > > > I propose to remove this se

Re: Release a 3.2

[Philippe Mouawad]

Hello,
I've filled New and Noteworthy section, feel free to improve.
I've also documented migration to new logging.

I think we can now release the 3.2 except for this bug which exists since
many versions, I've attached a patch for review:
- https://bz.apache.org/bugzilla/show_bug.cgi?id=60830

Regards

On Mon, Mar 6, 2017 at 10:14 PM, Antonio Gomes Rodrigues <ra0...@gmail.com>
wrote:

> Hi,
>
> Modifications in the PR done
>
> Antonio
>
> 2017-03-06 15:51 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:
>
> > Hi Philippe
> >
> > 2017-03-06 8:40 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:
> >
> >> Hello Antonio,
> >> I 've reviewed it rapidly:
> >> - button at the bottom => In nightly build it is at top now and buttons
> >> have changed
> >>
> > Ok, I will modify it
> >
> >
> >> - With the gui, but it's not recommended to big load test => With the
> gui,
> >> but just during debug phase, use Non GUI for your load test.
> >>
> > Ok, I will modify it
> >
> >
> >>
> >> I think you should mention that between Validation phase and Run phase
> >> there is variabilization and Correlation phase.
> >>
> > Not added because it's not present in the original document
> > I will mention it and add some tips
> >
> > Antonio
> >
> >>
> >> Thanks
> >> Regards
> >>
> >> On Sun, Mar 5, 2017 at 7:10 PM, Antonio Gomes Rodrigues <
> ra0...@gmail.com
> >> >
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > I have modified jmeter proxy step by step document
> >> >
> >> > See my modifications in https://github.com/apache/jmeter/pull/279
> >> >
> >> > If it's ok, I will commit it in svn
> >> >
> >> > Antonio
> >> >
> >> > 2017-03-02 10:47 GMT+01:00 Maxime Chassagneux <
> >> > maxime.chassagn...@gmail.com>
> >> > :
> >> >
> >> > > Hi,
> >> > >
> >> > > I have to update some screen + documentation for the JMS change made
> >> by
> >> > me.
> >> > > I will do it ASAP.
> >> > >
> >> > >
> >> > > 2017-03-01 23:36 GMT+01:00 Antonio Gomes Rodrigues <
> ra0...@gmail.com
> >> >:
> >> > >
> >> > > > 2017-03-01 23:03 GMT+01:00 Philippe Mouawad <
> >> > philippe.moua...@gmail.com
> >> > > >:
> >> > > >
> >> > > > > On Wed, Mar 1, 2017 at 10:59 PM, Antonio Gomes Rodrigues <
> >> > > > ra0...@gmail.com
> >> > > > > >
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Hi,
> >> > > > > >
> >> > > > > > 1.
> >> > > > > > One question, in jmeter_tutorial.html file we talk about a
> >> > screenshot
> >> > > > > which
> >> > > > > > exit in pdf file but not in html file: "From the screen
> >> capture, we
> >> > > see
> >> > > > > the
> >> > > > > > following directories. "
> >> > > > > >
> >> > > > > > I propose to remove this sentence instead of adding the screen
> >> > > > > >
> >> > > > >
> >> > > > > +1
> >> > > > >
> >> > > >
> >> > > > Done
> >> > > >
> >> > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > Later we talk about:
> >> > > > > >
> >> > > > > > "monitortomcat 5 monitor components"
> >> > > > > >
> >> > > > > >
> >> > > > > > "htmlparsera snapshot of HtmlParser, donated by HtmlParser
> >> project
> >> > on
> >> > > > > > sourceforge"
> >> > > > > >
> >> > > > > > These folders don't exist anymore, can I remove them?
> >> > > > > >
> >> > > > > +1
> >> > > > >
> >> > > >
> >> > > > Done
> >> > > >
> >> > > > >
> >> > 

Re: Release a 3.2

[Antonio Gomes Rodrigues]

is not needed.
>> > > > >
>> > > > In these conditions, I think we need to had more general cases where
>> > > access
>> > > > logs might be inappropriate.
>> > > > I will work on it tomorrow
>> > > >
>> > > >
>> > > > >
>> > > > > >
>> > > > > >
>> > > > > > 3.
>> > > > > >
>> > > > > > About jmeter_proxy_step_by_step.html
>> > > > > >
>> > > > > > I think we need to write it again to talk to all the new
>> features
>> > > > > > (template...)
>> > > > > >
>> > > > > > I can do it this week
>> > > > > >
>> > > > > +1
>> > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Antonio
>> > > > > >
>> > > > > >
>> > > > > > 2017-03-01 22:30 GMT+01:00 Antonio Gomes Rodrigues <
>> > ra0...@gmail.com
>> > > >:
>> > > > > >
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > my fault, the PDF links have been removed
>> > > > > > >
>> > > > > > > I check the 5 files and give a feedback asap
>> > > > > > >
>> > > > > > > Antonio
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > 2017-03-01 22:16 GMT+01:00 Philippe Mouawad <
>> > > > > philippe.moua...@gmail.com
>> > > > > > >:
>> > > > > > >
>> > > > > > >> Hi Antonio,
>> > > > > > >> I removed PDF links, are you sure you generated last docs ?
>> > > > > > >> Thanks
>> > > > > > >>
>> > > > > > >> On Wed, Mar 1, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
>> > > > > > >> ra0...@gmail.com>
>> > > > > > >> wrote:
>> > > > > > >>
>> > > > > > >> > Thanks,
>> > > > > > >> >
>> > > > > > >> > Is it normal that pdf file still exist and the link in the
>> > left
>> > > > > > >> (Tutorials
>> > > > > > >> > (PDF format)) are sill to pdf files?
>> > > > > > >> >
>> > > > > > >> > Antonio
>> > > > > > >> >
>> > > > > > >> > 2017-03-01 21:52 GMT+01:00 Felix Schumacher <
>> > > > > > >> > felix.schumac...@internetallee.de>:
>> > > > > > >> >
>> > > > > > >> > > Am 01.03.2017 um 21:07 schrieb Antonio Gomes Rodrigues:
>> > > > > > >> > >
>> > > > > > >> > >> Hi,
>> > > > > > >> > >>
>> > > > > > >> > >> About " Ensure the migrated docs (from PDF) do not
>> contain
>> > > old
>> > > > > > "Urban
>> > > > > > >> > >> legends"
>> > > > > > >> > >> :-) nor bad practices. Those are the 4 Tutorial
>> links
>> > in
>> > > > left
>> > > > > > >> menu.
>> > > > > > >> > It
>> > > > > > >> > >> would be nice to review them. I've fixed some but
>> not
>> > > done
>> > > > > the
>> > > > > > >> full
>> > > > > > >> > >> work"
>> > > > > > >> > >>
>> > > > > > >> > >> Which files are?
>> > > > > > >> > >>
>> > > > > > >> > > Look for xml files in the xdocs folder, which are named
>> as
>> > the
>> > > > > > >> tutorials
>> > > > > > >> > > on the jmeter homepage in the menu. They should be:
>> > > > > > >> > >
>> > > > > > >> > >

Re: Release a 3.2

[Antonio Gomes Rodrigues]

; > >
> > > > > > I can do it this week
> > > > > >
> > > > > +1
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Antonio
> > > > > >
> > > > > >
> > > > > > 2017-03-01 22:30 GMT+01:00 Antonio Gomes Rodrigues <
> > ra0...@gmail.com
> > > >:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > my fault, the PDF links have been removed
> > > > > > >
> > > > > > > I check the 5 files and give a feedback asap
> > > > > > >
> > > > > > > Antonio
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 2017-03-01 22:16 GMT+01:00 Philippe Mouawad <
> > > > > philippe.moua...@gmail.com
> > > > > > >:
> > > > > > >
> > > > > > >> Hi Antonio,
> > > > > > >> I removed PDF links, are you sure you generated last docs ?
> > > > > > >> Thanks
> > > > > > >>
> > > > > > >> On Wed, Mar 1, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
> > > > > > >> ra0...@gmail.com>
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> > Thanks,
> > > > > > >> >
> > > > > > >> > Is it normal that pdf file still exist and the link in the
> > left
> > > > > > >> (Tutorials
> > > > > > >> > (PDF format)) are sill to pdf files?
> > > > > > >> >
> > > > > > >> > Antonio
> > > > > > >> >
> > > > > > >> > 2017-03-01 21:52 GMT+01:00 Felix Schumacher <
> > > > > > >> > felix.schumac...@internetallee.de>:
> > > > > > >> >
> > > > > > >> > > Am 01.03.2017 um 21:07 schrieb Antonio Gomes Rodrigues:
> > > > > > >> > >
> > > > > > >> > >> Hi,
> > > > > > >> > >>
> > > > > > >> > >> About " Ensure the migrated docs (from PDF) do not
> contain
> > > old
> > > > > > "Urban
> > > > > > >> > >> legends"
> > > > > > >> > >> :-) nor bad practices. Those are the 4 Tutorial links
> > in
> > > > left
> > > > > > >> menu.
> > > > > > >> > It
> > > > > > >> > >> would be nice to review them. I've fixed some but not
> > > done
> > > > > the
> > > > > > >> full
> > > > > > >> > >> work"
> > > > > > >> > >>
> > > > > > >> > >> Which files are?
> > > > > > >> > >>
> > > > > > >> > > Look for xml files in the xdocs folder, which are named as
> > the
> > > > > > >> tutorials
> > > > > > >> > > on the jmeter homepage in the menu. They should be:
> > > > > > >> > >
> > > > > > >> > > xdocs/usermanual/jmeter_distributed_testing_step_by_
> > step.xml
> > > > > > >> > > xdocs/usermanual/jmeter_proxy_step_by_step.xml
> > > > > > >> > > xdocs/usermanual/junitsampler_tutorial.xml
> > > > > > >> > > xdocs/usermanual/jmeter_accesslog_sampler_step_by_
> step.xml
> > > > > > >> > > xdocs/usermanual/jmeter_tutorial.xml
> > > > > > >> > >
> > > > > > >> > > Felix
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> > >> Thanks
> > > > > > >> > >> Antonio
> > > > > > >> > >>
> > > > > > >> > >> 2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <
> > > > > > ra0...@gmail.com
> > > > > 

Re: Release a 3.2

[Philippe Mouawad]

lippe Mouawad <
> > > > philippe.moua...@gmail.com
> > > > > >:
> > > > > >
> > > > > >> Hi Antonio,
> > > > > >> I removed PDF links, are you sure you generated last docs ?
> > > > > >> Thanks
> > > > > >>
> > > > > >> On Wed, Mar 1, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
> > > > > >> ra0...@gmail.com>
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Thanks,
> > > > > >> >
> > > > > >> > Is it normal that pdf file still exist and the link in the
> left
> > > > > >> (Tutorials
> > > > > >> > (PDF format)) are sill to pdf files?
> > > > > >> >
> > > > > >> > Antonio
> > > > > >> >
> > > > > >> > 2017-03-01 21:52 GMT+01:00 Felix Schumacher <
> > > > > >> > felix.schumac...@internetallee.de>:
> > > > > >> >
> > > > > >> > > Am 01.03.2017 um 21:07 schrieb Antonio Gomes Rodrigues:
> > > > > >> > >
> > > > > >> > >> Hi,
> > > > > >> > >>
> > > > > >> > >> About " Ensure the migrated docs (from PDF) do not contain
> > old
> > > > > "Urban
> > > > > >> > >> legends"
> > > > > >> > >> :-) nor bad practices. Those are the 4 Tutorial links
> in
> > > left
> > > > > >> menu.
> > > > > >> > It
> > > > > >> > >> would be nice to review them. I've fixed some but not
> > done
> > > > the
> > > > > >> full
> > > > > >> > >> work"
> > > > > >> > >>
> > > > > >> > >> Which files are?
> > > > > >> > >>
> > > > > >> > > Look for xml files in the xdocs folder, which are named as
> the
> > > > > >> tutorials
> > > > > >> > > on the jmeter homepage in the menu. They should be:
> > > > > >> > >
> > > > > >> > > xdocs/usermanual/jmeter_distributed_testing_step_by_
> step.xml
> > > > > >> > > xdocs/usermanual/jmeter_proxy_step_by_step.xml
> > > > > >> > > xdocs/usermanual/junitsampler_tutorial.xml
> > > > > >> > > xdocs/usermanual/jmeter_accesslog_sampler_step_by_step.xml
> > > > > >> > > xdocs/usermanual/jmeter_tutorial.xml
> > > > > >> > >
> > > > > >> > > Felix
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >> Thanks
> > > > > >> > >> Antonio
> > > > > >> > >>
> > > > > >> > >> 2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <
> > > > > ra0...@gmail.com
> > > > > >> >:
> > > > > >> > >>
> > > > > >> > >> Hi,
> > > > > >> > >>>
> > > > > >> > >>> 2017-02-28 22:54 GMT+01:00 Philippe Mouawad <
> > > > > >> > philippe.moua...@gmail.com
> > > > > >> > >>> >:
> > > > > >> > >>>
> > > > > >> > >>> Hello,
> > > > > >> > >>>> We're now at:
> > > > > >> > >>>>
> > > > > >> > >>>> - 48 Enhancements
> > > > > >> > >>>> - 31 bug fixes
> > > > > >> > >>>>
> > > > > >> > >>>> Sebb has fixed Windows failures on Jenkins
> > > > > >> > >>>>
> > > > > >> > >>>> - Ensure the migrated docs (from PDF) do not contain
> > old
> > > > > "Urban
> > > > > >> > >>>> legends"
> > > > > >> > >>>> :-) nor bad practices. Those are the 4 Tutorial links
> > in
> &

Re: Release a 3.2

[Antonio Gomes Rodrigues]

017 um 21:07 schrieb Antonio Gomes Rodrigues:
> > > > >> > >
> > > > >> > >> Hi,
> > > > >> > >>
> > > > >> > >> About " Ensure the migrated docs (from PDF) do not contain
> old
> > > > "Urban
> > > > >> > >> legends"
> > > > >> > >> :-) nor bad practices. Those are the 4 Tutorial links in
> > left
> > > > >> menu.
> > > > >> > It
> > > > >> > >> would be nice to review them. I've fixed some but not
> done
> > > the
> > > > >> full
> > > > >> > >> work"
> > > > >> > >>
> > > > >> > >> Which files are?
> > > > >> > >>
> > > > >> > > Look for xml files in the xdocs folder, which are named as the
> > > > >> tutorials
> > > > >> > > on the jmeter homepage in the menu. They should be:
> > > > >> > >
> > > > >> > > xdocs/usermanual/jmeter_distributed_testing_step_by_step.xml
> > > > >> > > xdocs/usermanual/jmeter_proxy_step_by_step.xml
> > > > >> > > xdocs/usermanual/junitsampler_tutorial.xml
> > > > >> > > xdocs/usermanual/jmeter_accesslog_sampler_step_by_step.xml
> > > > >> > > xdocs/usermanual/jmeter_tutorial.xml
> > > > >> > >
> > > > >> > > Felix
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > >> Thanks
> > > > >> > >> Antonio
> > > > >> > >>
> > > > >> > >> 2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <
> > > > ra0...@gmail.com
> > > > >> >:
> > > > >> > >>
> > > > >> > >> Hi,
> > > > >> > >>>
> > > > >> > >>> 2017-02-28 22:54 GMT+01:00 Philippe Mouawad <
> > > > >> > philippe.moua...@gmail.com
> > > > >> > >>> >:
> > > > >> > >>>
> > > > >> > >>> Hello,
> > > > >> > >>>> We're now at:
> > > > >> > >>>>
> > > > >> > >>>> - 48 Enhancements
> > > > >> > >>>> - 31 bug fixes
> > > > >> > >>>>
> > > > >> > >>>> Sebb has fixed Windows failures on Jenkins
> > > > >> > >>>>
> > > > >> > >>>> - Ensure the migrated docs (from PDF) do not contain
> old
> > > > "Urban
> > > > >> > >>>> legends"
> > > > >> > >>>> :-) nor bad practices. Those are the 4 Tutorial links
> in
> > > left
> > > > >> > menu.
> > > > >> > >>>> It
> > > > >> > >>>> would be nice to review them. I've fixed some but not
> > done
> > > > the
> > > > >> > full
> > > > >> > >>>> work
> > > > >> > >>>>
> > > > >> > >>>> TODO
> > > > >> > >>>>
> > > > >> > >>>> I will check them today
> > > > >> > >>>
> > > > >> > >>>
> > > > >> > >>>
> > > > >> > >>> - Fill in introduced properties in
> > properties_reference.xml
> > > > >> > >>>>
> > > > >> > >>>> DONE
> > > > >> > >>>>
> > > > >> > >>>> - If possible add JUnits on the regression introduced
> in
> > > GET
> > > > >> with
> > > > >> > no
> > > > >> > >>>> body (see my mail)
> > > > >> > >>>>
> > > > >> > >>>> DONE
> > > > >> > >>>>
> > > > >> > >>>> - Fill in New and Noteworthy section
> > > > >> > >>>>
> > > > >> > >>>> TODO
> > > > >> > >>>>
> > > > >> > >>>>
> > > > >> > >>>> Are you ok to start a release soon ?
> > > > >> > >>>>
> > > > >> > >>>> Ok
> > > > >> > >>>
> > > > >> > >>>
> > > > >> > >>>
> > > > >> > >>> Thanks
> > > > >> > >>>>
> > > > >> > >>>> Regards
> > > > >> > >>>>
> > > > >> > >>>> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com>
> > > wrote:
> > > > >> > >>>>
> > > > >> > >>>> I'm seeing some test failures on Windows.
> > > > >> > >>>>>
> > > > >> > >>>>> I've started to set up a Jenkins build to be able to catch
> > > > these.
> > > > >> > >>>>> (at present the failure mails are sent direct to me)
> > > > >> > >>>>>
> > > > >> > >>>>> Depending on the cause, the failures need to be fixed
> before
> > > the
> > > > >> next
> > > > >> > >>>>> release.
> > > > >> > >>>>>
> > > > >> > >>>>> On 11 February 2017 at 10:22, Philippe Mouawad
> > > > >> > >>>>> <philippe.moua...@gmail.com> wrote:
> > > > >> > >>>>>
> > > > >> > >>>>>> Hello,
> > > > >> > >>>>>> Since our discussion on "Release a 3.2 ?" , trunk has
> > nicely
> > > > >> > evolved:
> > > > >> > >>>>>>
> > > > >> > >>>>>> - 33 Enhancements
> > > > >> > >>>>>> - 25 bug fixes
> > > > >> > >>>>>>
> > > > >> > >>>>>> I think we can now plan a release.
> > > > >> > >>>>>>
> > > > >> > >>>>>> I see the following remaining work:
> > > > >> > >>>>>>
> > > > >> > >>>>>> - Ensure the migrated docs (from PDF) do not contain
> > old
> > > > >> "Urban
> > > > >> > >>>>>>
> > > > >> > >>>>> legends"
> > > > >> > >>>>>
> > > > >> > >>>>>> :-) nor bad practices. Those are the 4 Tutorial links
> > in
> > > > left
> > > > >> > >>>>>>
> > > > >> > >>>>> menu. It
> > > > >> > >>>>
> > > > >> > >>>>> would be nice to review them. I've fixed some but not
> > done
> > > > the
> > > > >> > full
> > > > >> > >>>>>>
> > > > >> > >>>>> work
> > > > >> > >>>>>
> > > > >> > >>>>>> - Fill in introduced properties in
> > > properties_reference.xml
> > > > >> > >>>>>> - If possible add JUnits on the regression introduced
> > in
> > > > GET
> > > > >> > with
> > > > >> > >>>>>>
> > > > >> > >>>>> no
> > > > >> > >>>>
> > > > >> > >>>>> body (see my mail)
> > > > >> > >>>>>> - Fill in New and Noteworthy section
> > > > >> > >>>>>>
> > > > >> > >>>>>>
> > > > >> > >>>>>>
> > > > >> > >>>>>> --
> > > > >> > >>>>>> Cordialement.
> > > > >> > >>>>>> Philippe Mouawad.
> > > > >> > >>>>>>
> > > > >> > >>>>>
> > > > >> > >>>>
> > > > >> > >>>> --
> > > > >> > >>>> Cordialement.
> > > > >> > >>>> Philippe Mouawad.
> > > > >> > >>>>
> > > > >> > >>>>
> > > > >> > >>>
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Cordialement.
> > > > >> Philippe Mouawad.
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Cordialement.
> > > Philippe Mouawad.
> > >
> >
>

Re: Release a 3.2

[Maxime Chassagneux]

 the
> > > >> tutorials
> > > >> > > on the jmeter homepage in the menu. They should be:
> > > >> > >
> > > >> > > xdocs/usermanual/jmeter_distributed_testing_step_by_step.xml
> > > >> > > xdocs/usermanual/jmeter_proxy_step_by_step.xml
> > > >> > > xdocs/usermanual/junitsampler_tutorial.xml
> > > >> > > xdocs/usermanual/jmeter_accesslog_sampler_step_by_step.xml
> > > >> > > xdocs/usermanual/jmeter_tutorial.xml
> > > >> > >
> > > >> > > Felix
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > >> Thanks
> > > >> > >> Antonio
> > > >> > >>
> > > >> > >> 2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <
> > > ra0...@gmail.com
> > > >> >:
> > > >> > >>
> > > >> > >> Hi,
> > > >> > >>>
> > > >> > >>> 2017-02-28 22:54 GMT+01:00 Philippe Mouawad <
> > > >> > philippe.moua...@gmail.com
> > > >> > >>> >:
> > > >> > >>>
> > > >> > >>> Hello,
> > > >> > >>>> We're now at:
> > > >> > >>>>
> > > >> > >>>> - 48 Enhancements
> > > >> > >>>> - 31 bug fixes
> > > >> > >>>>
> > > >> > >>>> Sebb has fixed Windows failures on Jenkins
> > > >> > >>>>
> > > >> > >>>> - Ensure the migrated docs (from PDF) do not contain old
> > > "Urban
> > > >> > >>>> legends"
> > > >> > >>>> :-) nor bad practices. Those are the 4 Tutorial links in
> > left
> > > >> > menu.
> > > >> > >>>> It
> > > >> > >>>> would be nice to review them. I've fixed some but not
> done
> > > the
> > > >> > full
> > > >> > >>>> work
> > > >> > >>>>
> > > >> > >>>> TODO
> > > >> > >>>>
> > > >> > >>>> I will check them today
> > > >> > >>>
> > > >> > >>>
> > > >> > >>>
> > > >> > >>> - Fill in introduced properties in
> properties_reference.xml
> > > >> > >>>>
> > > >> > >>>> DONE
> > > >> > >>>>
> > > >> > >>>> - If possible add JUnits on the regression introduced in
> > GET
> > > >> with
> > > >> > no
> > > >> > >>>> body (see my mail)
> > > >> > >>>>
> > > >> > >>>> DONE
> > > >> > >>>>
> > > >> > >>>> - Fill in New and Noteworthy section
> > > >> > >>>>
> > > >> > >>>> TODO
> > > >> > >>>>
> > > >> > >>>>
> > > >> > >>>> Are you ok to start a release soon ?
> > > >> > >>>>
> > > >> > >>>> Ok
> > > >> > >>>
> > > >> > >>>
> > > >> > >>>
> > > >> > >>> Thanks
> > > >> > >>>>
> > > >> > >>>> Regards
> > > >> > >>>>
> > > >> > >>>> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com>
> > wrote:
> > > >> > >>>>
> > > >> > >>>> I'm seeing some test failures on Windows.
> > > >> > >>>>>
> > > >> > >>>>> I've started to set up a Jenkins build to be able to catch
> > > these.
> > > >> > >>>>> (at present the failure mails are sent direct to me)
> > > >> > >>>>>
> > > >> > >>>>> Depending on the cause, the failures need to be fixed before
> > the
> > > >> next
> > > >> > >>>>> release.
> > > >> > >>>>>
> > > >> > >>>>> On 11 February 2017 at 10:22, Philippe Mouawad
> > > >> > >>>>> <philippe.moua...@gmail.com> wrote:
> > > >> > >>>>>
> > > >> > >>>>>> Hello,
> > > >> > >>>>>> Since our discussion on "Release a 3.2 ?" , trunk has
> nicely
> > > >> > evolved:
> > > >> > >>>>>>
> > > >> > >>>>>> - 33 Enhancements
> > > >> > >>>>>> - 25 bug fixes
> > > >> > >>>>>>
> > > >> > >>>>>> I think we can now plan a release.
> > > >> > >>>>>>
> > > >> > >>>>>> I see the following remaining work:
> > > >> > >>>>>>
> > > >> > >>>>>> - Ensure the migrated docs (from PDF) do not contain
> old
> > > >> "Urban
> > > >> > >>>>>>
> > > >> > >>>>> legends"
> > > >> > >>>>>
> > > >> > >>>>>> :-) nor bad practices. Those are the 4 Tutorial links
> in
> > > left
> > > >> > >>>>>>
> > > >> > >>>>> menu. It
> > > >> > >>>>
> > > >> > >>>>> would be nice to review them. I've fixed some but not
> done
> > > the
> > > >> > full
> > > >> > >>>>>>
> > > >> > >>>>> work
> > > >> > >>>>>
> > > >> > >>>>>> - Fill in introduced properties in
> > properties_reference.xml
> > > >> > >>>>>> - If possible add JUnits on the regression introduced
> in
> > > GET
> > > >> > with
> > > >> > >>>>>>
> > > >> > >>>>> no
> > > >> > >>>>
> > > >> > >>>>> body (see my mail)
> > > >> > >>>>>> - Fill in New and Noteworthy section
> > > >> > >>>>>>
> > > >> > >>>>>>
> > > >> > >>>>>>
> > > >> > >>>>>> --
> > > >> > >>>>>> Cordialement.
> > > >> > >>>>>> Philippe Mouawad.
> > > >> > >>>>>>
> > > >> > >>>>>
> > > >> > >>>>
> > > >> > >>>> --
> > > >> > >>>> Cordialement.
> > > >> > >>>> Philippe Mouawad.
> > > >> > >>>>
> > > >> > >>>>
> > > >> > >>>
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Cordialement.
> > > >> Philippe Mouawad.
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
>

Re: Release a 3.2

[Antonio Gomes Rodrigues]

onio Gomes Rodrigues <
> > ra0...@gmail.com
> > >> >:
> > >> > >>
> > >> > >> Hi,
> > >> > >>>
> > >> > >>> 2017-02-28 22:54 GMT+01:00 Philippe Mouawad <
> > >> > philippe.moua...@gmail.com
> > >> > >>> >:
> > >> > >>>
> > >> > >>> Hello,
> > >> > >>>> We're now at:
> > >> > >>>>
> > >> > >>>> - 48 Enhancements
> > >> > >>>> - 31 bug fixes
> > >> > >>>>
> > >> > >>>> Sebb has fixed Windows failures on Jenkins
> > >> > >>>>
> > >> > >>>> - Ensure the migrated docs (from PDF) do not contain old
> > "Urban
> > >> > >>>> legends"
> > >> > >>>> :-) nor bad practices. Those are the 4 Tutorial links in
> left
> > >> > menu.
> > >> > >>>> It
> > >> > >>>> would be nice to review them. I've fixed some but not done
> > the
> > >> > full
> > >> > >>>> work
> > >> > >>>>
> > >> > >>>> TODO
> > >> > >>>>
> > >> > >>>> I will check them today
> > >> > >>>
> > >> > >>>
> > >> > >>>
> > >> > >>> - Fill in introduced properties in properties_reference.xml
> > >> > >>>>
> > >> > >>>> DONE
> > >> > >>>>
> > >> > >>>> - If possible add JUnits on the regression introduced in
> GET
> > >> with
> > >> > no
> > >> > >>>> body (see my mail)
> > >> > >>>>
> > >> > >>>> DONE
> > >> > >>>>
> > >> > >>>> - Fill in New and Noteworthy section
> > >> > >>>>
> > >> > >>>> TODO
> > >> > >>>>
> > >> > >>>>
> > >> > >>>> Are you ok to start a release soon ?
> > >> > >>>>
> > >> > >>>> Ok
> > >> > >>>
> > >> > >>>
> > >> > >>>
> > >> > >>> Thanks
> > >> > >>>>
> > >> > >>>> Regards
> > >> > >>>>
> > >> > >>>> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com>
> wrote:
> > >> > >>>>
> > >> > >>>> I'm seeing some test failures on Windows.
> > >> > >>>>>
> > >> > >>>>> I've started to set up a Jenkins build to be able to catch
> > these.
> > >> > >>>>> (at present the failure mails are sent direct to me)
> > >> > >>>>>
> > >> > >>>>> Depending on the cause, the failures need to be fixed before
> the
> > >> next
> > >> > >>>>> release.
> > >> > >>>>>
> > >> > >>>>> On 11 February 2017 at 10:22, Philippe Mouawad
> > >> > >>>>> <philippe.moua...@gmail.com> wrote:
> > >> > >>>>>
> > >> > >>>>>> Hello,
> > >> > >>>>>> Since our discussion on "Release a 3.2 ?" , trunk has nicely
> > >> > evolved:
> > >> > >>>>>>
> > >> > >>>>>> - 33 Enhancements
> > >> > >>>>>> - 25 bug fixes
> > >> > >>>>>>
> > >> > >>>>>> I think we can now plan a release.
> > >> > >>>>>>
> > >> > >>>>>> I see the following remaining work:
> > >> > >>>>>>
> > >> > >>>>>> - Ensure the migrated docs (from PDF) do not contain old
> > >> "Urban
> > >> > >>>>>>
> > >> > >>>>> legends"
> > >> > >>>>>
> > >> > >>>>>> :-) nor bad practices. Those are the 4 Tutorial links in
> > left
> > >> > >>>>>>
> > >> > >>>>> menu. It
> > >> > >>>>
> > >> > >>>>> would be nice to review them. I've fixed some but not done
> > the
> > >> > full
> > >> > >>>>>>
> > >> > >>>>> work
> > >> > >>>>>
> > >> > >>>>>> - Fill in introduced properties in
> properties_reference.xml
> > >> > >>>>>> - If possible add JUnits on the regression introduced in
> > GET
> > >> > with
> > >> > >>>>>>
> > >> > >>>>> no
> > >> > >>>>
> > >> > >>>>> body (see my mail)
> > >> > >>>>>> - Fill in New and Noteworthy section
> > >> > >>>>>>
> > >> > >>>>>>
> > >> > >>>>>>
> > >> > >>>>>> --
> > >> > >>>>>> Cordialement.
> > >> > >>>>>> Philippe Mouawad.
> > >> > >>>>>>
> > >> > >>>>>
> > >> > >>>>
> > >> > >>>> --
> > >> > >>>> Cordialement.
> > >> > >>>> Philippe Mouawad.
> > >> > >>>>
> > >> > >>>>
> > >> > >>>
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Cordialement.
> > >> Philippe Mouawad.
> > >>
> > >
> > >
> >
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>

Re: Release a 3.2

[Philippe Mouawad]

gt;> :-) nor bad practices. Those are the 4 Tutorial links in left
> >> > menu.
> >> > >>>> It
> >> > >>>> would be nice to review them. I've fixed some but not done
> the
> >> > full
> >> > >>>> work
> >> > >>>>
> >> > >>>> TODO
> >> > >>>>
> >> > >>>> I will check them today
> >> > >>>
> >> > >>>
> >> > >>>
> >> > >>> - Fill in introduced properties in properties_reference.xml
> >> > >>>>
> >> > >>>> DONE
> >> > >>>>
> >> > >>>> - If possible add JUnits on the regression introduced in GET
> >> with
> >> > no
> >> > >>>> body (see my mail)
> >> > >>>>
> >> > >>>> DONE
> >> > >>>>
> >> > >>>> - Fill in New and Noteworthy section
> >> > >>>>
> >> > >>>> TODO
> >> > >>>>
> >> > >>>>
> >> > >>>> Are you ok to start a release soon ?
> >> > >>>>
> >> > >>>> Ok
> >> > >>>
> >> > >>>
> >> > >>>
> >> > >>> Thanks
> >> > >>>>
> >> > >>>> Regards
> >> > >>>>
> >> > >>>> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
> >> > >>>>
> >> > >>>> I'm seeing some test failures on Windows.
> >> > >>>>>
> >> > >>>>> I've started to set up a Jenkins build to be able to catch
> these.
> >> > >>>>> (at present the failure mails are sent direct to me)
> >> > >>>>>
> >> > >>>>> Depending on the cause, the failures need to be fixed before the
> >> next
> >> > >>>>> release.
> >> > >>>>>
> >> > >>>>> On 11 February 2017 at 10:22, Philippe Mouawad
> >> > >>>>> <philippe.moua...@gmail.com> wrote:
> >> > >>>>>
> >> > >>>>>> Hello,
> >> > >>>>>> Since our discussion on "Release a 3.2 ?" , trunk has nicely
> >> > evolved:
> >> > >>>>>>
> >> > >>>>>> - 33 Enhancements
> >> > >>>>>> - 25 bug fixes
> >> > >>>>>>
> >> > >>>>>> I think we can now plan a release.
> >> > >>>>>>
> >> > >>>>>> I see the following remaining work:
> >> > >>>>>>
> >> > >>>>>> - Ensure the migrated docs (from PDF) do not contain old
> >> "Urban
> >> > >>>>>>
> >> > >>>>> legends"
> >> > >>>>>
> >> > >>>>>> :-) nor bad practices. Those are the 4 Tutorial links in
> left
> >> > >>>>>>
> >> > >>>>> menu. It
> >> > >>>>
> >> > >>>>> would be nice to review them. I've fixed some but not done
> the
> >> > full
> >> > >>>>>>
> >> > >>>>> work
> >> > >>>>>
> >> > >>>>>> - Fill in introduced properties in properties_reference.xml
> >> > >>>>>> - If possible add JUnits on the regression introduced in
> GET
> >> > with
> >> > >>>>>>
> >> > >>>>> no
> >> > >>>>
> >> > >>>>> body (see my mail)
> >> > >>>>>> - Fill in New and Noteworthy section
> >> > >>>>>>
> >> > >>>>>>
> >> > >>>>>>
> >> > >>>>>> --
> >> > >>>>>> Cordialement.
> >> > >>>>>> Philippe Mouawad.
> >> > >>>>>>
> >> > >>>>>
> >> > >>>>
> >> > >>>> --
> >> > >>>> Cordialement.
> >> > >>>> Philippe Mouawad.
> >> > >>>>
> >> > >>>>
> >> > >>>
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Cordialement.
> >> Philippe Mouawad.
> >>
> >
> >
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release a 3.2

[Antonio Gomes Rodrigues]

Hi,

1.
One question, in jmeter_tutorial.html file we talk about a screenshot which
exit in pdf file but not in html file: "From the screen capture, we see the
following directories. "

I propose to remove this sentence instead of adding the screen


Later we talk about:

"monitortomcat 5 monitor components"


"htmlparsera snapshot of HtmlParser, donated by HtmlParser project on
sourceforge"

These folders don't exist anymore, can I remove them?


If you are ok, I can make the modifications now


2.

About jmeter_accesslog_sampler_step_by_step.html file

My opinion is that this is a gadget and I have never seen someone make
serious load test with access.log file (no correlation between url...)

I think we need to remove it from homepage


3.

About jmeter_proxy_step_by_step.html

I think we need to write it again to talk to all the new features
(template...)

I can do it this week



Antonio


2017-03-01 22:30 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:

> Hi,
>
> my fault, the PDF links have been removed
>
> I check the 5 files and give a feedback asap
>
> Antonio
>
>
>
> 2017-03-01 22:16 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:
>
>> Hi Antonio,
>> I removed PDF links, are you sure you generated last docs ?
>> Thanks
>>
>> On Wed, Mar 1, 2017 at 10:14 PM, Antonio Gomes Rodrigues <
>> ra0...@gmail.com>
>> wrote:
>>
>> > Thanks,
>> >
>> > Is it normal that pdf file still exist and the link in the left
>> (Tutorials
>> > (PDF format)) are sill to pdf files?
>> >
>> > Antonio
>> >
>> > 2017-03-01 21:52 GMT+01:00 Felix Schumacher <
>> > felix.schumac...@internetallee.de>:
>> >
>> > > Am 01.03.2017 um 21:07 schrieb Antonio Gomes Rodrigues:
>> > >
>> > >> Hi,
>> > >>
>> > >> About " Ensure the migrated docs (from PDF) do not contain old "Urban
>> > >> legends"
>> > >> :-) nor bad practices. Those are the 4 Tutorial links in left
>> menu.
>> > It
>> > >> would be nice to review them. I've fixed some but not done the
>> full
>> > >> work"
>> > >>
>> > >> Which files are?
>> > >>
>> > > Look for xml files in the xdocs folder, which are named as the
>> tutorials
>> > > on the jmeter homepage in the menu. They should be:
>> > >
>> > > xdocs/usermanual/jmeter_distributed_testing_step_by_step.xml
>> > > xdocs/usermanual/jmeter_proxy_step_by_step.xml
>> > > xdocs/usermanual/junitsampler_tutorial.xml
>> > > xdocs/usermanual/jmeter_accesslog_sampler_step_by_step.xml
>> > > xdocs/usermanual/jmeter_tutorial.xml
>> > >
>> > > Felix
>> > >
>> > >
>> > >
>> > >> Thanks
>> > >> Antonio
>> > >>
>> > >> 2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com
>> >:
>> > >>
>> > >> Hi,
>> > >>>
>> > >>> 2017-02-28 22:54 GMT+01:00 Philippe Mouawad <
>> > philippe.moua...@gmail.com
>> > >>> >:
>> > >>>
>> > >>> Hello,
>> > >>>> We're now at:
>> > >>>>
>> > >>>> - 48 Enhancements
>> > >>>> - 31 bug fixes
>> > >>>>
>> > >>>> Sebb has fixed Windows failures on Jenkins
>> > >>>>
>> > >>>> - Ensure the migrated docs (from PDF) do not contain old "Urban
>> > >>>> legends"
>> > >>>> :-) nor bad practices. Those are the 4 Tutorial links in left
>> > menu.
>> > >>>> It
>> > >>>> would be nice to review them. I've fixed some but not done the
>> > full
>> > >>>> work
>> > >>>>
>> > >>>> TODO
>> > >>>>
>> > >>>> I will check them today
>> > >>>
>> > >>>
>> > >>>
>> > >>> - Fill in introduced properties in properties_reference.xml
>> > >>>>
>> > >>>> DONE
>> > >>>>
>> > >>>> - If possible add JUnits on the regression introduced in GET
>> with
>> > no
>> > >>>> body (see my mail)
>> > >&g

Re: Release a 3.2

[Philippe Mouawad]

Hi Antonio,
I removed PDF links, are you sure you generated last docs ?
Thanks

On Wed, Mar 1, 2017 at 10:14 PM, Antonio Gomes Rodrigues <ra0...@gmail.com>
wrote:

> Thanks,
>
> Is it normal that pdf file still exist and the link in the left (Tutorials
> (PDF format)) are sill to pdf files?
>
> Antonio
>
> 2017-03-01 21:52 GMT+01:00 Felix Schumacher <
> felix.schumac...@internetallee.de>:
>
> > Am 01.03.2017 um 21:07 schrieb Antonio Gomes Rodrigues:
> >
> >> Hi,
> >>
> >> About " Ensure the migrated docs (from PDF) do not contain old "Urban
> >> legends"
> >> :-) nor bad practices. Those are the 4 Tutorial links in left menu.
> It
> >> would be nice to review them. I've fixed some but not done the full
> >> work"
> >>
> >> Which files are?
> >>
> > Look for xml files in the xdocs folder, which are named as the tutorials
> > on the jmeter homepage in the menu. They should be:
> >
> > xdocs/usermanual/jmeter_distributed_testing_step_by_step.xml
> > xdocs/usermanual/jmeter_proxy_step_by_step.xml
> > xdocs/usermanual/junitsampler_tutorial.xml
> > xdocs/usermanual/jmeter_accesslog_sampler_step_by_step.xml
> > xdocs/usermanual/jmeter_tutorial.xml
> >
> > Felix
> >
> >
> >
> >> Thanks
> >> Antonio
> >>
> >> 2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:
> >>
> >> Hi,
> >>>
> >>> 2017-02-28 22:54 GMT+01:00 Philippe Mouawad <
> philippe.moua...@gmail.com
> >>> >:
> >>>
> >>> Hello,
> >>>> We're now at:
> >>>>
> >>>> - 48 Enhancements
> >>>> - 31 bug fixes
> >>>>
> >>>> Sebb has fixed Windows failures on Jenkins
> >>>>
> >>>> - Ensure the migrated docs (from PDF) do not contain old "Urban
> >>>> legends"
> >>>> :-) nor bad practices. Those are the 4 Tutorial links in left
> menu.
> >>>> It
> >>>> would be nice to review them. I've fixed some but not done the
> full
> >>>> work
> >>>>
> >>>> TODO
> >>>>
> >>>> I will check them today
> >>>
> >>>
> >>>
> >>> - Fill in introduced properties in properties_reference.xml
> >>>>
> >>>> DONE
> >>>>
> >>>> - If possible add JUnits on the regression introduced in GET with
> no
> >>>> body (see my mail)
> >>>>
> >>>> DONE
> >>>>
> >>>> - Fill in New and Noteworthy section
> >>>>
> >>>> TODO
> >>>>
> >>>>
> >>>> Are you ok to start a release soon ?
> >>>>
> >>>> Ok
> >>>
> >>>
> >>>
> >>> Thanks
> >>>>
> >>>> Regards
> >>>>
> >>>> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
> >>>>
> >>>> I'm seeing some test failures on Windows.
> >>>>>
> >>>>> I've started to set up a Jenkins build to be able to catch these.
> >>>>> (at present the failure mails are sent direct to me)
> >>>>>
> >>>>> Depending on the cause, the failures need to be fixed before the next
> >>>>> release.
> >>>>>
> >>>>> On 11 February 2017 at 10:22, Philippe Mouawad
> >>>>> <philippe.moua...@gmail.com> wrote:
> >>>>>
> >>>>>> Hello,
> >>>>>> Since our discussion on "Release a 3.2 ?" , trunk has nicely
> evolved:
> >>>>>>
> >>>>>> - 33 Enhancements
> >>>>>> - 25 bug fixes
> >>>>>>
> >>>>>> I think we can now plan a release.
> >>>>>>
> >>>>>> I see the following remaining work:
> >>>>>>
> >>>>>> - Ensure the migrated docs (from PDF) do not contain old "Urban
> >>>>>>
> >>>>> legends"
> >>>>>
> >>>>>> :-) nor bad practices. Those are the 4 Tutorial links in left
> >>>>>>
> >>>>> menu. It
> >>>>
> >>>>> would be nice to review them. I've fixed some but not done the
> full
> >>>>>>
> >>>>> work
> >>>>>
> >>>>>> - Fill in introduced properties in properties_reference.xml
> >>>>>> - If possible add JUnits on the regression introduced in GET
> with
> >>>>>>
> >>>>> no
> >>>>
> >>>>> body (see my mail)
> >>>>>> - Fill in New and Noteworthy section
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Cordialement.
> >>>>>> Philippe Mouawad.
> >>>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> Cordialement.
> >>>> Philippe Mouawad.
> >>>>
> >>>>
> >>>
> >
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release a 3.2

[Antonio Gomes Rodrigues]

Thanks,

Is it normal that pdf file still exist and the link in the left (Tutorials
(PDF format)) are sill to pdf files?

Antonio

2017-03-01 21:52 GMT+01:00 Felix Schumacher <
felix.schumac...@internetallee.de>:

> Am 01.03.2017 um 21:07 schrieb Antonio Gomes Rodrigues:
>
>> Hi,
>>
>> About " Ensure the migrated docs (from PDF) do not contain old "Urban
>> legends"
>> :-) nor bad practices. Those are the 4 Tutorial links in left menu. It
>> would be nice to review them. I've fixed some but not done the full
>> work"
>>
>> Which files are?
>>
> Look for xml files in the xdocs folder, which are named as the tutorials
> on the jmeter homepage in the menu. They should be:
>
> xdocs/usermanual/jmeter_distributed_testing_step_by_step.xml
> xdocs/usermanual/jmeter_proxy_step_by_step.xml
> xdocs/usermanual/junitsampler_tutorial.xml
> xdocs/usermanual/jmeter_accesslog_sampler_step_by_step.xml
> xdocs/usermanual/jmeter_tutorial.xml
>
> Felix
>
>
>
>> Thanks
>> Antonio
>>
>> 2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:
>>
>> Hi,
>>>
>>> 2017-02-28 22:54 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com
>>> >:
>>>
>>> Hello,
>>>> We're now at:
>>>>
>>>> - 48 Enhancements
>>>> - 31 bug fixes
>>>>
>>>> Sebb has fixed Windows failures on Jenkins
>>>>
>>>> - Ensure the migrated docs (from PDF) do not contain old "Urban
>>>> legends"
>>>> :-) nor bad practices. Those are the 4 Tutorial links in left menu.
>>>> It
>>>> would be nice to review them. I've fixed some but not done the full
>>>> work
>>>>
>>>> TODO
>>>>
>>>> I will check them today
>>>
>>>
>>>
>>> - Fill in introduced properties in properties_reference.xml
>>>>
>>>> DONE
>>>>
>>>> - If possible add JUnits on the regression introduced in GET with no
>>>> body (see my mail)
>>>>
>>>> DONE
>>>>
>>>> - Fill in New and Noteworthy section
>>>>
>>>> TODO
>>>>
>>>>
>>>> Are you ok to start a release soon ?
>>>>
>>>> Ok
>>>
>>>
>>>
>>> Thanks
>>>>
>>>> Regards
>>>>
>>>> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
>>>>
>>>> I'm seeing some test failures on Windows.
>>>>>
>>>>> I've started to set up a Jenkins build to be able to catch these.
>>>>> (at present the failure mails are sent direct to me)
>>>>>
>>>>> Depending on the cause, the failures need to be fixed before the next
>>>>> release.
>>>>>
>>>>> On 11 February 2017 at 10:22, Philippe Mouawad
>>>>> <philippe.moua...@gmail.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>> Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved:
>>>>>>
>>>>>> - 33 Enhancements
>>>>>> - 25 bug fixes
>>>>>>
>>>>>> I think we can now plan a release.
>>>>>>
>>>>>> I see the following remaining work:
>>>>>>
>>>>>> - Ensure the migrated docs (from PDF) do not contain old "Urban
>>>>>>
>>>>> legends"
>>>>>
>>>>>> :-) nor bad practices. Those are the 4 Tutorial links in left
>>>>>>
>>>>> menu. It
>>>>
>>>>> would be nice to review them. I've fixed some but not done the full
>>>>>>
>>>>> work
>>>>>
>>>>>> - Fill in introduced properties in properties_reference.xml
>>>>>> - If possible add JUnits on the regression introduced in GET with
>>>>>>
>>>>> no
>>>>
>>>>> body (see my mail)
>>>>>> - Fill in New and Noteworthy section
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cordialement.
>>>>>> Philippe Mouawad.
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Cordialement.
>>>> Philippe Mouawad.
>>>>
>>>>
>>>
>

Re: Release a 3.2

[Felix Schumacher]

Am 01.03.2017 um 21:07 schrieb Antonio Gomes Rodrigues:

Hi,

About " Ensure the migrated docs (from PDF) do not contain old "Urban
legends"
:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
would be nice to review them. I've fixed some but not done the full work"

Which files are?
Look for xml files in the xdocs folder, which are named as the tutorials 
on the jmeter homepage in the menu. They should be:


xdocs/usermanual/jmeter_distributed_testing_step_by_step.xml
xdocs/usermanual/jmeter_proxy_step_by_step.xml
xdocs/usermanual/junitsampler_tutorial.xml
xdocs/usermanual/jmeter_accesslog_sampler_step_by_step.xml
xdocs/usermanual/jmeter_tutorial.xml

Felix



Thanks
Antonio

2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:


Hi,

2017-02-28 22:54 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:


Hello,
We're now at:

- 48 Enhancements
- 31 bug fixes

Sebb has fixed Windows failures on Jenkins

- Ensure the migrated docs (from PDF) do not contain old "Urban
legends"
:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
would be nice to review them. I've fixed some but not done the full
work

TODO


I will check them today




- Fill in introduced properties in properties_reference.xml

DONE

- If possible add JUnits on the regression introduced in GET with no
body (see my mail)

DONE

- Fill in New and Noteworthy section

TODO


Are you ok to start a release soon ?


Ok




Thanks

Regards

On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:


I'm seeing some test failures on Windows.

I've started to set up a Jenkins build to be able to catch these.
(at present the failure mails are sent direct to me)

Depending on the cause, the failures need to be fixed before the next
release.

On 11 February 2017 at 10:22, Philippe Mouawad
<philippe.moua...@gmail.com> wrote:

Hello,
Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved:

- 33 Enhancements
- 25 bug fixes

I think we can now plan a release.

I see the following remaining work:

- Ensure the migrated docs (from PDF) do not contain old "Urban

legends"

:-) nor bad practices. Those are the 4 Tutorial links in left

menu. It

would be nice to review them. I've fixed some but not done the full

work

- Fill in introduced properties in properties_reference.xml
- If possible add JUnits on the regression introduced in GET with

no

body (see my mail)
- Fill in New and Noteworthy section



--
Cordialement.
Philippe Mouawad.



--
Cordialement.
Philippe Mouawad.

Re: Release a 3.2

[Antonio Gomes Rodrigues]

Hi,

About " Ensure the migrated docs (from PDF) do not contain old "Urban
legends"
   :-) nor bad practices. Those are the 4 Tutorial links in left menu. It
   would be nice to review them. I've fixed some but not done the full work"

Which files are?

Thanks
Antonio

2017-03-01 10:44 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:

> Hi,
>
> 2017-02-28 22:54 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:
>
>> Hello,
>> We're now at:
>>
>>- 48 Enhancements
>>- 31 bug fixes
>>
>> Sebb has fixed Windows failures on Jenkins
>>
>>- Ensure the migrated docs (from PDF) do not contain old "Urban
>> legends"
>>:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
>>would be nice to review them. I've fixed some but not done the full
>> work
>>
>> TODO
>>
>
> I will check them today
>
>
>
>>
>>- Fill in introduced properties in properties_reference.xml
>>
>> DONE
>>
>>- If possible add JUnits on the regression introduced in GET with no
>>body (see my mail)
>>
>> DONE
>>
>>- Fill in New and Noteworthy section
>>
>> TODO
>>
>>
>> Are you ok to start a release soon ?
>>
>
> Ok
>
>
>
>>
>> Thanks
>>
>> Regards
>>
>> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
>>
>> > I'm seeing some test failures on Windows.
>> >
>> > I've started to set up a Jenkins build to be able to catch these.
>> > (at present the failure mails are sent direct to me)
>> >
>> > Depending on the cause, the failures need to be fixed before the next
>> > release.
>> >
>> > On 11 February 2017 at 10:22, Philippe Mouawad
>> > <philippe.moua...@gmail.com> wrote:
>> > > Hello,
>> > > Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved:
>> > >
>> > >- 33 Enhancements
>> > >- 25 bug fixes
>> > >
>> > > I think we can now plan a release.
>> > >
>> > > I see the following remaining work:
>> > >
>> > >- Ensure the migrated docs (from PDF) do not contain old "Urban
>> > legends"
>> > >:-) nor bad practices. Those are the 4 Tutorial links in left
>> menu. It
>> > >would be nice to review them. I've fixed some but not done the full
>> > work
>> > >- Fill in introduced properties in properties_reference.xml
>> > >- If possible add JUnits on the regression introduced in GET with
>> no
>> > >body (see my mail)
>> > >- Fill in New and Noteworthy section
>> > >
>> > >
>> > >
>> > > --
>> > > Cordialement.
>> > > Philippe Mouawad.
>> >
>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>
>

Re: Release a 3.2

[Antonio Gomes Rodrigues]

Hi,

2017-02-28 22:54 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:

> Hello,
> We're now at:
>
>- 48 Enhancements
>- 31 bug fixes
>
> Sebb has fixed Windows failures on Jenkins
>
>- Ensure the migrated docs (from PDF) do not contain old "Urban legends"
>:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
>would be nice to review them. I've fixed some but not done the full work
>
> TODO
>

I will check them today



>
>- Fill in introduced properties in properties_reference.xml
>
> DONE
>
>- If possible add JUnits on the regression introduced in GET with no
>body (see my mail)
>
> DONE
>
>- Fill in New and Noteworthy section
>
> TODO
>
>
> Are you ok to start a release soon ?
>

Ok



>
> Thanks
>
> Regards
>
> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
>
> > I'm seeing some test failures on Windows.
> >
> > I've started to set up a Jenkins build to be able to catch these.
> > (at present the failure mails are sent direct to me)
> >
> > Depending on the cause, the failures need to be fixed before the next
> > release.
> >
> > On 11 February 2017 at 10:22, Philippe Mouawad
> > <philippe.moua...@gmail.com> wrote:
> > > Hello,
> > > Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved:
> > >
> > >- 33 Enhancements
> > >- 25 bug fixes
> > >
> > > I think we can now plan a release.
> > >
> > > I see the following remaining work:
> > >
> > >- Ensure the migrated docs (from PDF) do not contain old "Urban
> > legends"
> > >:-) nor bad practices. Those are the 4 Tutorial links in left menu.
> It
> > >would be nice to review them. I've fixed some but not done the full
> > work
> > >- Fill in introduced properties in properties_reference.xml
> > >- If possible add JUnits on the regression introduced in GET with no
> > >body (see my mail)
> > >- Fill in New and Noteworthy section
> > >
> > >
> > >
> > > --
> > > Cordialement.
> > > Philippe Mouawad.
> >
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>

Re: Release a 3.2

[Philippe Mouawad]

> >>
> >> >> jmeter.properties used to describe this in some detail.
> >> >> The updated description probably does not belong there, but there
> >> >> should at least be a pointer to where to find the new information.
> >> >>
> >> >> >>
> >> >> >> Remove remaining references to older logging API.
> >> >> >>
> >> >> >
> >> >> > Where ?
> >> >> > I thought I had done it
> >> >>
> >> >> The string log_level appears in quite a few places.
> >> >> AFAIK it is not used in the new scheme
> >> >>
> >> > I have removed them.
> >> > Let me know if I still missed something
> >>
> >> I don't know if there is anything else.
> >> I just happened to notice that reference.
> >>
> >> Thanks for pointing that
> >
> >
> >> >  Thanks
> >> >
> >> >>
> >> >> >>
> >> >> >> >
> >> >> >> > DONE
> >> >> >> >
> >> >> >> >- If possible add JUnits on the regression introduced in GET
> >> with
> >> >> no
> >> >> >> >body (see my mail)
> >> >> >> >
> >> >> >> > DONE
> >> >> >> >
> >> >> >> >- Fill in New and Noteworthy section
> >> >> >> >
> >> >> >> > TODO
> >> >> >> >
> >> >> >> >
> >> >> >> > Are you ok to start a release soon ?
> >> >> >> >
> >> >> >> > Thanks
> >> >> >> >
> >> >> >> > Regards
> >> >> >> >
> >> >> >> > On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com
> >> <javascript:;>> wrote:
> >> >> >> >
> >> >> >> >> I'm seeing some test failures on Windows.
> >> >> >> >>
> >> >> >> >> I've started to set up a Jenkins build to be able to catch
> these.
> >> >> >> >> (at present the failure mails are sent direct to me)
> >> >> >> >>
> >> >> >> >> Depending on the cause, the failures need to be fixed before
> the
> >> next
> >> >> >> >> release.
> >> >> >> >>
> >> >> >> >> On 11 February 2017 at 10:22, Philippe Mouawad
> >> >> >> >> <philippe.moua...@gmail.com <javascript:;>> wrote:
> >> >> >> >> > Hello,
> >> >> >> >> > Since our discussion on "Release a 3.2 ?" , trunk has nicely
> >> >> evolved:
> >> >> >> >> >
> >> >> >> >> >- 33 Enhancements
> >> >> >> >> >- 25 bug fixes
> >> >> >> >> >
> >> >> >> >> > I think we can now plan a release.
> >> >> >> >> >
> >> >> >> >> > I see the following remaining work:
> >> >> >> >> >
> >> >> >> >> >- Ensure the migrated docs (from PDF) do not contain old
> >> "Urban
> >> >> >> >> legends"
> >> >> >> >> >:-) nor bad practices. Those are the 4 Tutorial links in
> left
> >> >> >> menu. It
> >> >> >> >> >would be nice to review them. I've fixed some but not done
> >> the
> >> >> full
> >> >> >> >> work
> >> >> >> >> >- Fill in introduced properties in
> properties_reference.xml
> >> >> >> >> >- If possible add JUnits on the regression introduced in
> GET
> >> >> with
> >> >> >> no
> >> >> >> >> >body (see my mail)
> >> >> >> >> >- Fill in New and Noteworthy section
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > Cordialement.
> >> >> >> >> > Philippe Mouawad.
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Cordialement.
> >> >> >> > Philippe Mouawad.
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Cordialement.
> >> >> > Philippe Mouawad.
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Cordialement.
> >> > Philippe Mouawad.
> >>
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release a 3.2

[sebb]

On 28 February 2017 at 22:40, Philippe Mouawad
<philippe.moua...@gmail.com> wrote:
> On Tue, Feb 28, 2017 at 11:25 PM, sebb <seb...@gmail.com> wrote:
>
>> On 28 February 2017 at 22:06, Philippe Mouawad
>> <philippe.moua...@gmail.com> wrote:
>> > On Tue, Feb 28, 2017 at 11:01 PM, sebb <seb...@gmail.com> wrote:
>> >
>> >> On 28 February 2017 at 21:54, Philippe Mouawad
>> >> <philippe.moua...@gmail.com> wrote:
>> >> > Hello,
>> >> > We're now at:
>> >> >
>> >> >- 48 Enhancements
>> >> >- 31 bug fixes
>> >> >
>> >> > Sebb has fixed Windows failures on Jenkins
>> >> >
>> >> >- Ensure the migrated docs (from PDF) do not contain old "Urban
>> >> legends"
>> >> >:-) nor bad practices. Those are the 4 Tutorial links in left
>> menu. It
>> >> >would be nice to review them. I've fixed some but not done the full
>> >> work
>> >> >
>> >> > TODO
>> >> >
>> >> >- Fill in introduced properties in properties_reference.xml
>> >>
>> >> Remove obsolete references (e.g. some logging ones ?)
>> >>
>> >
>> > Which ones ?
>> > I made the cleanup.
>> > Did I forget something ?
>> >
>> >>
>> >> Add logging documentation.
>> >>
>> > It has been done in properties_reference.xml
>>
>> There is only some mention of HttpClient logging there.
>>
>> I could not find any description as to how to set the level for a
>> specific JMeter class.
>>
>
> I think this is pretty easy to find on internet knowing we use log4j2 and
> slf4j.
> But if you think we should add some doc, feel free to do it.

Sorry, but that is not good enough.
I did not want the hassle of changing the logging. You did want the change.
The change was agreed to on the basis that updated documentation was essential.

There do not need to be reams of docs, but there should be at least
couple of sentences as to how to configure the logging that will be
readily understandable to someone used to the old ways.

And plugin writers need to be told how to update their plugins.

>>
>> jmeter.properties used to describe this in some detail.
>> The updated description probably does not belong there, but there
>> should at least be a pointer to where to find the new information.
>>
>> >>
>> >> Remove remaining references to older logging API.
>> >>
>> >
>> > Where ?
>> > I thought I had done it
>>
>> The string log_level appears in quite a few places.
>> AFAIK it is not used in the new scheme
>>
> I have removed them.
> Let me know if I still missed something

I don't know if there is anything else.
I just happened to notice that reference.

>  Thanks
>
>>
>> >>
>> >> >
>> >> > DONE
>> >> >
>> >> >- If possible add JUnits on the regression introduced in GET with
>> no
>> >> >body (see my mail)
>> >> >
>> >> > DONE
>> >> >
>> >> >- Fill in New and Noteworthy section
>> >> >
>> >> > TODO
>> >> >
>> >> >
>> >> > Are you ok to start a release soon ?
>> >> >
>> >> > Thanks
>> >> >
>> >> > Regards
>> >> >
>> >> > On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
>> >> >
>> >> >> I'm seeing some test failures on Windows.
>> >> >>
>> >> >> I've started to set up a Jenkins build to be able to catch these.
>> >> >> (at present the failure mails are sent direct to me)
>> >> >>
>> >> >> Depending on the cause, the failures need to be fixed before the next
>> >> >> release.
>> >> >>
>> >> >> On 11 February 2017 at 10:22, Philippe Mouawad
>> >> >> <philippe.moua...@gmail.com> wrote:
>> >> >> > Hello,
>> >> >> > Since our discussion on "Release a 3.2 ?" , trunk has nicely
>> evolved:
>> >> >> >
>> >> >> >- 33 Enhancements
>> >> >> >- 25 bug fixes
>> >> >> >
>> >> >> > I think we can now plan a release.
>> >> >> >
>> >> >> > I see the following remaining work:
>> >> >> >
>> >> >> >- Ensure the migrated docs (from PDF) do not contain old "Urban
>> >> >> legends"
>> >> >> >:-) nor bad practices. Those are the 4 Tutorial links in left
>> >> menu. It
>> >> >> >would be nice to review them. I've fixed some but not done the
>> full
>> >> >> work
>> >> >> >- Fill in introduced properties in properties_reference.xml
>> >> >> >- If possible add JUnits on the regression introduced in GET
>> with
>> >> no
>> >> >> >body (see my mail)
>> >> >> >- Fill in New and Noteworthy section
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cordialement.
>> >> >> > Philippe Mouawad.
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cordialement.
>> >> > Philippe Mouawad.
>> >>
>> >
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: Release a 3.2

[Philippe Mouawad]

On Tue, Feb 28, 2017 at 11:25 PM, sebb <seb...@gmail.com> wrote:

> On 28 February 2017 at 22:06, Philippe Mouawad
> <philippe.moua...@gmail.com> wrote:
> > On Tue, Feb 28, 2017 at 11:01 PM, sebb <seb...@gmail.com> wrote:
> >
> >> On 28 February 2017 at 21:54, Philippe Mouawad
> >> <philippe.moua...@gmail.com> wrote:
> >> > Hello,
> >> > We're now at:
> >> >
> >> >- 48 Enhancements
> >> >- 31 bug fixes
> >> >
> >> > Sebb has fixed Windows failures on Jenkins
> >> >
> >> >- Ensure the migrated docs (from PDF) do not contain old "Urban
> >> legends"
> >> >:-) nor bad practices. Those are the 4 Tutorial links in left
> menu. It
> >> >would be nice to review them. I've fixed some but not done the full
> >> work
> >> >
> >> > TODO
> >> >
> >> >- Fill in introduced properties in properties_reference.xml
> >>
> >> Remove obsolete references (e.g. some logging ones ?)
> >>
> >
> > Which ones ?
> > I made the cleanup.
> > Did I forget something ?
> >
> >>
> >> Add logging documentation.
> >>
> > It has been done in properties_reference.xml
>
> There is only some mention of HttpClient logging there.
>
> I could not find any description as to how to set the level for a
> specific JMeter class.
>

I think this is pretty easy to find on internet knowing we use log4j2 and
slf4j.
But if you think we should add some doc, feel free to do it.

>
> jmeter.properties used to describe this in some detail.
> The updated description probably does not belong there, but there
> should at least be a pointer to where to find the new information.
>
> >>
> >> Remove remaining references to older logging API.
> >>
> >
> > Where ?
> > I thought I had done it
>
> The string log_level appears in quite a few places.
> AFAIK it is not used in the new scheme
>
I have removed them.
Let me know if I still missed something
 Thanks

>
> >>
> >> >
> >> > DONE
> >> >
> >> >- If possible add JUnits on the regression introduced in GET with
> no
> >> >body (see my mail)
> >> >
> >> > DONE
> >> >
> >> >- Fill in New and Noteworthy section
> >> >
> >> > TODO
> >> >
> >> >
> >> > Are you ok to start a release soon ?
> >> >
> >> > Thanks
> >> >
> >> > Regards
> >> >
> >> > On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
> >> >
> >> >> I'm seeing some test failures on Windows.
> >> >>
> >> >> I've started to set up a Jenkins build to be able to catch these.
> >> >> (at present the failure mails are sent direct to me)
> >> >>
> >> >> Depending on the cause, the failures need to be fixed before the next
> >> >> release.
> >> >>
> >> >> On 11 February 2017 at 10:22, Philippe Mouawad
> >> >> <philippe.moua...@gmail.com> wrote:
> >> >> > Hello,
> >> >> > Since our discussion on "Release a 3.2 ?" , trunk has nicely
> evolved:
> >> >> >
> >> >> >- 33 Enhancements
> >> >> >- 25 bug fixes
> >> >> >
> >> >> > I think we can now plan a release.
> >> >> >
> >> >> > I see the following remaining work:
> >> >> >
> >> >> >- Ensure the migrated docs (from PDF) do not contain old "Urban
> >> >> legends"
> >> >> >:-) nor bad practices. Those are the 4 Tutorial links in left
> >> menu. It
> >> >> >would be nice to review them. I've fixed some but not done the
> full
> >> >> work
> >> >> >- Fill in introduced properties in properties_reference.xml
> >> >> >- If possible add JUnits on the regression introduced in GET
> with
> >> no
> >> >> >body (see my mail)
> >> >> >- Fill in New and Noteworthy section
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Cordialement.
> >> >> > Philippe Mouawad.
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Cordialement.
> >> > Philippe Mouawad.
> >>
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release a 3.2

[sebb]

On 28 February 2017 at 22:06, Philippe Mouawad
<philippe.moua...@gmail.com> wrote:
> On Tue, Feb 28, 2017 at 11:01 PM, sebb <seb...@gmail.com> wrote:
>
>> On 28 February 2017 at 21:54, Philippe Mouawad
>> <philippe.moua...@gmail.com> wrote:
>> > Hello,
>> > We're now at:
>> >
>> >- 48 Enhancements
>> >- 31 bug fixes
>> >
>> > Sebb has fixed Windows failures on Jenkins
>> >
>> >- Ensure the migrated docs (from PDF) do not contain old "Urban
>> legends"
>> >:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
>> >would be nice to review them. I've fixed some but not done the full
>> work
>> >
>> > TODO
>> >
>> >- Fill in introduced properties in properties_reference.xml
>>
>> Remove obsolete references (e.g. some logging ones ?)
>>
>
> Which ones ?
> I made the cleanup.
> Did I forget something ?
>
>>
>> Add logging documentation.
>>
> It has been done in properties_reference.xml

There is only some mention of HttpClient logging there.

I could not find any description as to how to set the level for a
specific JMeter class.

jmeter.properties used to describe this in some detail.
The updated description probably does not belong there, but there
should at least be a pointer to where to find the new information.

>>
>> Remove remaining references to older logging API.
>>
>
> Where ?
> I thought I had done it

The string log_level appears in quite a few places.
AFAIK it is not used in the new scheme

>>
>> >
>> > DONE
>> >
>> >- If possible add JUnits on the regression introduced in GET with no
>> >body (see my mail)
>> >
>> > DONE
>> >
>> >- Fill in New and Noteworthy section
>> >
>> > TODO
>> >
>> >
>> > Are you ok to start a release soon ?
>> >
>> > Thanks
>> >
>> > Regards
>> >
>> > On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
>> >
>> >> I'm seeing some test failures on Windows.
>> >>
>> >> I've started to set up a Jenkins build to be able to catch these.
>> >> (at present the failure mails are sent direct to me)
>> >>
>> >> Depending on the cause, the failures need to be fixed before the next
>> >> release.
>> >>
>> >> On 11 February 2017 at 10:22, Philippe Mouawad
>> >> <philippe.moua...@gmail.com> wrote:
>> >> > Hello,
>> >> > Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved:
>> >> >
>> >> >- 33 Enhancements
>> >> >- 25 bug fixes
>> >> >
>> >> > I think we can now plan a release.
>> >> >
>> >> > I see the following remaining work:
>> >> >
>> >> >- Ensure the migrated docs (from PDF) do not contain old "Urban
>> >> legends"
>> >> >:-) nor bad practices. Those are the 4 Tutorial links in left
>> menu. It
>> >> >would be nice to review them. I've fixed some but not done the full
>> >> work
>> >> >- Fill in introduced properties in properties_reference.xml
>> >> >- If possible add JUnits on the regression introduced in GET with
>> no
>> >> >body (see my mail)
>> >> >- Fill in New and Noteworthy section
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cordialement.
>> >> > Philippe Mouawad.
>> >>
>> >
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: Release a 3.2

[Philippe Mouawad]

On Tue, Feb 28, 2017 at 11:01 PM, sebb <seb...@gmail.com> wrote:

> On 28 February 2017 at 21:54, Philippe Mouawad
> <philippe.moua...@gmail.com> wrote:
> > Hello,
> > We're now at:
> >
> >- 48 Enhancements
> >- 31 bug fixes
> >
> > Sebb has fixed Windows failures on Jenkins
> >
> >- Ensure the migrated docs (from PDF) do not contain old "Urban
> legends"
> >:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
> >would be nice to review them. I've fixed some but not done the full
> work
> >
> > TODO
> >
> >- Fill in introduced properties in properties_reference.xml
>
> Remove obsolete references (e.g. some logging ones ?)
>

Which ones ?
I made the cleanup.
Did I forget something ?

>
> Add logging documentation.
>
It has been done in properties_reference.xml

>
> Remove remaining references to older logging API.
>

Where ?
I thought I had done it

>
> >
> > DONE
> >
> >- If possible add JUnits on the regression introduced in GET with no
> >body (see my mail)
> >
> > DONE
> >
> >- Fill in New and Noteworthy section
> >
> > TODO
> >
> >
> > Are you ok to start a release soon ?
> >
> > Thanks
> >
> > Regards
> >
> > On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
> >
> >> I'm seeing some test failures on Windows.
> >>
> >> I've started to set up a Jenkins build to be able to catch these.
> >> (at present the failure mails are sent direct to me)
> >>
> >> Depending on the cause, the failures need to be fixed before the next
> >> release.
> >>
> >> On 11 February 2017 at 10:22, Philippe Mouawad
> >> <philippe.moua...@gmail.com> wrote:
> >> > Hello,
> >> > Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved:
> >> >
> >> >- 33 Enhancements
> >> >- 25 bug fixes
> >> >
> >> > I think we can now plan a release.
> >> >
> >> > I see the following remaining work:
> >> >
> >> >- Ensure the migrated docs (from PDF) do not contain old "Urban
> >> legends"
> >> >:-) nor bad practices. Those are the 4 Tutorial links in left
> menu. It
> >> >would be nice to review them. I've fixed some but not done the full
> >> work
> >> >- Fill in introduced properties in properties_reference.xml
> >> >- If possible add JUnits on the regression introduced in GET with
> no
> >> >body (see my mail)
> >> >- Fill in New and Noteworthy section
> >> >
> >> >
> >> >
> >> > --
> >> > Cordialement.
> >> > Philippe Mouawad.
> >>
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release a 3.2

[sebb]

On 28 February 2017 at 21:54, Philippe Mouawad
<philippe.moua...@gmail.com> wrote:
> Hello,
> We're now at:
>
>- 48 Enhancements
>- 31 bug fixes
>
> Sebb has fixed Windows failures on Jenkins
>
>- Ensure the migrated docs (from PDF) do not contain old "Urban legends"
>:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
>would be nice to review them. I've fixed some but not done the full work
>
> TODO
>
>- Fill in introduced properties in properties_reference.xml

Remove obsolete references (e.g. some logging ones ?)

Add logging documentation.

Remove remaining references to older logging API.

>
> DONE
>
>- If possible add JUnits on the regression introduced in GET with no
>body (see my mail)
>
> DONE
>
>- Fill in New and Noteworthy section
>
> TODO
>
>
> Are you ok to start a release soon ?
>
> Thanks
>
> Regards
>
> On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:
>
>> I'm seeing some test failures on Windows.
>>
>> I've started to set up a Jenkins build to be able to catch these.
>> (at present the failure mails are sent direct to me)
>>
>> Depending on the cause, the failures need to be fixed before the next
>> release.
>>
>> On 11 February 2017 at 10:22, Philippe Mouawad
>> <philippe.moua...@gmail.com> wrote:
>> > Hello,
>> > Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved:
>> >
>> >- 33 Enhancements
>> >- 25 bug fixes
>> >
>> > I think we can now plan a release.
>> >
>> > I see the following remaining work:
>> >
>> >- Ensure the migrated docs (from PDF) do not contain old "Urban
>> legends"
>> >:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
>> >would be nice to review them. I've fixed some but not done the full
>> work
>> >- Fill in introduced properties in properties_reference.xml
>> >- If possible add JUnits on the regression introduced in GET with no
>> >body (see my mail)
>> >- Fill in New and Noteworthy section
>> >
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: Release a 3.2

[Philippe Mouawad]

Hello,
We're now at:

   - 48 Enhancements
   - 31 bug fixes

Sebb has fixed Windows failures on Jenkins

   - Ensure the migrated docs (from PDF) do not contain old "Urban legends"
   :-) nor bad practices. Those are the 4 Tutorial links in left menu. It
   would be nice to review them. I've fixed some but not done the full work

TODO

   - Fill in introduced properties in properties_reference.xml

DONE

   - If possible add JUnits on the regression introduced in GET with no
   body (see my mail)

DONE

   - Fill in New and Noteworthy section

TODO


Are you ok to start a release soon ?

Thanks

Regards

On Tue, Feb 21, 2017 at 4:21 PM, sebb <seb...@gmail.com> wrote:

> I'm seeing some test failures on Windows.
>
> I've started to set up a Jenkins build to be able to catch these.
> (at present the failure mails are sent direct to me)
>
> Depending on the cause, the failures need to be fixed before the next
> release.
>
> On 11 February 2017 at 10:22, Philippe Mouawad
> <philippe.moua...@gmail.com> wrote:
> > Hello,
> > Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved:
> >
> >- 33 Enhancements
> >- 25 bug fixes
> >
> > I think we can now plan a release.
> >
> > I see the following remaining work:
> >
> >- Ensure the migrated docs (from PDF) do not contain old "Urban
> legends"
> >:-) nor bad practices. Those are the 4 Tutorial links in left menu. It
> >would be nice to review them. I've fixed some but not done the full
> work
> >- Fill in introduced properties in properties_reference.xml
> >- If possible add JUnits on the regression introduced in GET with no
> >body (see my mail)
> >- Fill in New and Noteworthy section
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release JMeter 3.2 ?

[Philippe Mouawad]

Hi,
Thanks.
Notice that for InfluxDB, I changed the annotations to events so that it's
easier for beginners to create the correct dashboard (example use this).
So it may break your existing dashboard on this part.

Thanks
Regards

On Mon, Jan 16, 2017 at 10:55 PM, Maxime Chassagneux <
maxime.chassagn...@gmail.com> wrote:

> Hi Philippe,
>
> I will deploy your nightly build in our permit to operate service tomorrow.
> It's the best way to test it :)
> Let me some days and come back to you quickly.
>
> Thanks.
>
> 2017-01-16 21:57 GMT+01:00 Philippe Mouawad :
>
> > Hello Maxime,
> > I merged some of your PR.
> > Did you have the opportunity to make tests of nightly build ?
> >
> > Your feedback is welcome.
> > Thanks
> > Regards
> >
> > On Fri, Jan 13, 2017 at 10:35 AM, Maxime Chassagneux <
> > maxime.chassagn...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Pls, could you consider to merge this PR too :
> > >
> > >  - PR-241 : Support variable for all JMS messages (bytes, object, ...)
> > and
> > > sources (file, folder)
> > >  - PR-240 : Improves JMS component robustness
> > >
> > > Thanks .
> > >
> > > 2017-01-12 21:02 GMT+01:00 Philippe Mouawad <
> philippe.moua...@gmail.com
> > >:
> > >
> > > > On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
> > > > felix.schumac...@internetallee.de> wrote:
> > > >
> > > > > Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
> > > > >
> > > > >> Hello,
> > > > >> What do you think of releasing a 3.2 version ?
> > > > >>
> > > > > I think I said before, that I would like to release often :)
> > > > >
> > > > >>
> > > > >> I see following reasons:
> > > > >>
> > > > >> - There is a regression (See bug 60575)
> > > > >>
> > > > > My fix for 60575 needs tests and review as it changes the contract
> of
> > > the
> > > > > method getSendParameterValuesAsPostBody.
> > > > >
> > > > I reviewed it , it looks ok to me.
> > > > I'll double check.
> > > >
> > > > >
> > > > > It returned true if there were no parameters (and thus none with a
> > > name).
> > > > > (Or if getPostBodyRaw() is true)
> > > > >
> > > > > After the change it returns only true when there are parameters and
> > > none
> > > > > of those have a name. (Or if getPostBodyRaw() is true).
> > > > >
> > > >
> > > >
> > > >
> > > > >
> > > > > This method is used in POST and PUT as well, but I believe the
> change
> > > to
> > > > > be correct in both places. too.
> > > > >
> > > > > - We have 9 enhancements and 12  Bug fixes
> > > > >> - Some nice features (at least as a current user I find them
> > > > >> interesting
> > > > >> :-) ):
> > > > >>- More space in UI and simpler look
> > > > >>- Up to date Browser based on javafx
> > > > >>
> > > > > We might have to warn a bit more about the need for javafx (The
> > default
> > > > > java for SUSE Leap42.2 seems to have no javafx). Without javafx
> > JMeter
> > > > will
> > > > > start, but the results tree view is missing.
> > > > >
> > > >
> > > > I think in this case we should try to fail in a bit cleaner way
> > > >
> > > > >- Or in response assertion
> > > > >>- Replace feature (partial)+ counting
> > > > >>
> > > > >> Maybe we can integrate before next release:
> > > > >>
> > > > >> - PR-247
> > > > >> - PR-246
> > > > >> - PR-245
> > > > >> - PR-237
> > > > >>
> > > > >> And upgrade some dependencies:
> > > > >>
> > > > >> - jodd which has a lot of perf enhancements that we use in
> > JMeter
> > > > (for
> > > > >> resources extractions)
> > > > >> - httpcomponents
> > > > >> - maybe more
> > > > >>
> > > > > I would like to link  the converted pdf tutorials and maybe do a
> bit
> > of
> > > > > minor tweaks to the look and feel of the web pages (less shadows).
> > > > >
> > > > > Should the sect-num number of the tutorials be continued from those
> > in
> > > > the
> > > > > usermanual section?
> > > > >
> > > >
> > > > I think so.
> > > >
> > > >
> > > > >> Besides, we did a lot of code changes related to sonar, let's
> > release
> > > > it.
> > > > >>
> > > > >> A last good thing is that we start to release more often.
> > > > >>
> > > > > +1
> > > > >
> > > > > Felix
> > > > >
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > > --
> > > > Cordialement.
> > > > Philippe Mouawad.
> > > >
> > >
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release JMeter 3.2 ?

[Antonio Gomes Rodrigues]

About G1, do you have a test case to check it and try to improve tuning?

Antonio

2017-01-16 22:31 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:

> On Mon, Jan 16, 2017 at 4:33 PM, Antonio Gomes Rodrigues <ra0...@gmail.com
> >
> wrote:
>
> > Hi,
> >
> > One more thing
> >
> > Release 3.2 will need Java 8. Is it the moment to switch to Nashorn
> Engine
> > by default?
> >
> +1 for me but we need to make it clear wherever Javascript is used:
>
>- IfController
>- __javascript function
>- properties reference
>- jmeter.properties
>- changes.xml as Incompatible change
>
>
>
> > Someone have made test with GC G1 to switch to it with the right
> parameter
> > in 3.2 release?
> >
> I've commited some changes and refreshed some old links and code.
> If anybody masters G1 , let him improve tuning.
>
> I didn't test on windows so if somebody can test everything is ok.
>
>
> >
> > Thank
> > Antonio
> >
> > 2017-01-16 10:13 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:
> >
> > > Hi Philippe,
> > >
> > > Thanks to your job
> > >
> > > 2017-01-15 23:20 GMT+01:00 Philippe Mouawad <
> philippe.moua...@gmail.com
> > >:
> > >
> > >> On Thu, Jan 12, 2017 at 9:02 PM, Philippe Mouawad <
> > >> philippe.moua...@gmail.com> wrote:
> > >>
> > >> >
> > >> >
> > >> > On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
> > >> > felix.schumac...@internetallee.de> wrote:
> > >> >
> > >> >> Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
> > >> >>
> > >> >>> Hello,
> > >> >>> What do you think of releasing a 3.2 version ?
> > >> >>>
> > >> >> I think I said before, that I would like to release often :)
> > >> >>
> > >> >>>
> > >> >>> I see following reasons:
> > >> >>>
> > >> >>> - There is a regression (See bug 60575)
> > >> >>>
> > >> >> My fix for 60575 needs tests and review as it changes the contract
> of
> > >> the
> > >> >> method getSendParameterValuesAsPostBody.
> > >> >>
> > >> > I reviewed it , it looks ok to me.
> > >> > I'll double check.
> > >> >
> > >> >>
> > >> >> It returned true if there were no parameters (and thus none with a
> > >> name).
> > >> >> (Or if getPostBodyRaw() is true)
> > >> >>
> > >> >> After the change it returns only true when there are parameters and
> > >> none
> > >> >> of those have a name. (Or if getPostBodyRaw() is true).
> > >> >>
> > >> >
> > >> >
> > >> >
> > >> >>
> > >> >> This method is used in POST and PUT as well, but I believe the
> change
> > >> to
> > >> >> be correct in both places. too.
> > >> >>
> > >> >> - We have 9 enhancements and 12  Bug fixes
> > >> >>> - Some nice features (at least as a current user I find them
> > >> >>> interesting
> > >> >>> :-) ):
> > >> >>>- More space in UI and simpler look
> > >> >>>- Up to date Browser based on javafx
> > >> >>>
> > >> >> We might have to warn a bit more about the need for javafx (The
> > default
> > >> >> java for SUSE Leap42.2 seems to have no javafx). Without javafx
> > JMeter
> > >> will
> > >> >> start, but the results tree view is missing.
> > >> >>
> > >> >
> > >> > I think in this case we should try to fail in a bit cleaner way
> > >> >
> > >>
> > >> Done through bug  60583
> > >> Still, not fully satisfied with solution as we catch a
> > >> NoClassDefFoundError
> > >> (I'll send a mail on this)
> > >>
> > >>
> > >>
> > >>- Or in response assertion
> > >> >>>- Replace feature (partial)+ counting
> > >> >>>
> > >> >>> Maybe we can integrate before next release:
> > &

Re: Release JMeter 3.2 ?

[Maxime Chassagneux]

Hi Philippe,

I will deploy your nightly build in our permit to operate service tomorrow.
It's the best way to test it :)
Let me some days and come back to you quickly.

Thanks.

2017-01-16 21:57 GMT+01:00 Philippe Mouawad :

> Hello Maxime,
> I merged some of your PR.
> Did you have the opportunity to make tests of nightly build ?
>
> Your feedback is welcome.
> Thanks
> Regards
>
> On Fri, Jan 13, 2017 at 10:35 AM, Maxime Chassagneux <
> maxime.chassagn...@gmail.com> wrote:
>
> > Hi,
> >
> > Pls, could you consider to merge this PR too :
> >
> >  - PR-241 : Support variable for all JMS messages (bytes, object, ...)
> and
> > sources (file, folder)
> >  - PR-240 : Improves JMS component robustness
> >
> > Thanks .
> >
> > 2017-01-12 21:02 GMT+01:00 Philippe Mouawad  >:
> >
> > > On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
> > > felix.schumac...@internetallee.de> wrote:
> > >
> > > > Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
> > > >
> > > >> Hello,
> > > >> What do you think of releasing a 3.2 version ?
> > > >>
> > > > I think I said before, that I would like to release often :)
> > > >
> > > >>
> > > >> I see following reasons:
> > > >>
> > > >> - There is a regression (See bug 60575)
> > > >>
> > > > My fix for 60575 needs tests and review as it changes the contract of
> > the
> > > > method getSendParameterValuesAsPostBody.
> > > >
> > > I reviewed it , it looks ok to me.
> > > I'll double check.
> > >
> > > >
> > > > It returned true if there were no parameters (and thus none with a
> > name).
> > > > (Or if getPostBodyRaw() is true)
> > > >
> > > > After the change it returns only true when there are parameters and
> > none
> > > > of those have a name. (Or if getPostBodyRaw() is true).
> > > >
> > >
> > >
> > >
> > > >
> > > > This method is used in POST and PUT as well, but I believe the change
> > to
> > > > be correct in both places. too.
> > > >
> > > > - We have 9 enhancements and 12  Bug fixes
> > > >> - Some nice features (at least as a current user I find them
> > > >> interesting
> > > >> :-) ):
> > > >>- More space in UI and simpler look
> > > >>- Up to date Browser based on javafx
> > > >>
> > > > We might have to warn a bit more about the need for javafx (The
> default
> > > > java for SUSE Leap42.2 seems to have no javafx). Without javafx
> JMeter
> > > will
> > > > start, but the results tree view is missing.
> > > >
> > >
> > > I think in this case we should try to fail in a bit cleaner way
> > >
> > > >- Or in response assertion
> > > >>- Replace feature (partial)+ counting
> > > >>
> > > >> Maybe we can integrate before next release:
> > > >>
> > > >> - PR-247
> > > >> - PR-246
> > > >> - PR-245
> > > >> - PR-237
> > > >>
> > > >> And upgrade some dependencies:
> > > >>
> > > >> - jodd which has a lot of perf enhancements that we use in
> JMeter
> > > (for
> > > >> resources extractions)
> > > >> - httpcomponents
> > > >> - maybe more
> > > >>
> > > > I would like to link  the converted pdf tutorials and maybe do a bit
> of
> > > > minor tweaks to the look and feel of the web pages (less shadows).
> > > >
> > > > Should the sect-num number of the tutorials be continued from those
> in
> > > the
> > > > usermanual section?
> > > >
> > >
> > > I think so.
> > >
> > >
> > > >> Besides, we did a lot of code changes related to sonar, let's
> release
> > > it.
> > > >>
> > > >> A last good thing is that we start to release more often.
> > > >>
> > > > +1
> > > >
> > > > Felix
> > > >
> > > >>
> > > >>
> > > >
> > >
> > >
> > > --
> > > Cordialement.
> > > Philippe Mouawad.
> > >
> >
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>

Re: Release JMeter 3.2 ?

[Philippe Mouawad]

On Mon, Jan 16, 2017 at 4:33 PM, Antonio Gomes Rodrigues <ra0...@gmail.com>
wrote:

> Hi,
>
> One more thing
>
> Release 3.2 will need Java 8. Is it the moment to switch to Nashorn Engine
> by default?
>
+1 for me but we need to make it clear wherever Javascript is used:

   - IfController
   - __javascript function
   - properties reference
   - jmeter.properties
   - changes.xml as Incompatible change



> Someone have made test with GC G1 to switch to it with the right parameter
> in 3.2 release?
>
I've commited some changes and refreshed some old links and code.
If anybody masters G1 , let him improve tuning.

I didn't test on windows so if somebody can test everything is ok.


>
> Thank
> Antonio
>
> 2017-01-16 10:13 GMT+01:00 Antonio Gomes Rodrigues <ra0...@gmail.com>:
>
> > Hi Philippe,
> >
> > Thanks to your job
> >
> > 2017-01-15 23:20 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com
> >:
> >
> >> On Thu, Jan 12, 2017 at 9:02 PM, Philippe Mouawad <
> >> philippe.moua...@gmail.com> wrote:
> >>
> >> >
> >> >
> >> > On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
> >> > felix.schumac...@internetallee.de> wrote:
> >> >
> >> >> Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
> >> >>
> >> >>> Hello,
> >> >>> What do you think of releasing a 3.2 version ?
> >> >>>
> >> >> I think I said before, that I would like to release often :)
> >> >>
> >> >>>
> >> >>> I see following reasons:
> >> >>>
> >> >>> - There is a regression (See bug 60575)
> >> >>>
> >> >> My fix for 60575 needs tests and review as it changes the contract of
> >> the
> >> >> method getSendParameterValuesAsPostBody.
> >> >>
> >> > I reviewed it , it looks ok to me.
> >> > I'll double check.
> >> >
> >> >>
> >> >> It returned true if there were no parameters (and thus none with a
> >> name).
> >> >> (Or if getPostBodyRaw() is true)
> >> >>
> >> >> After the change it returns only true when there are parameters and
> >> none
> >> >> of those have a name. (Or if getPostBodyRaw() is true).
> >> >>
> >> >
> >> >
> >> >
> >> >>
> >> >> This method is used in POST and PUT as well, but I believe the change
> >> to
> >> >> be correct in both places. too.
> >> >>
> >> >> - We have 9 enhancements and 12  Bug fixes
> >> >>> - Some nice features (at least as a current user I find them
> >> >>> interesting
> >> >>> :-) ):
> >> >>>- More space in UI and simpler look
> >> >>>- Up to date Browser based on javafx
> >> >>>
> >> >> We might have to warn a bit more about the need for javafx (The
> default
> >> >> java for SUSE Leap42.2 seems to have no javafx). Without javafx
> JMeter
> >> will
> >> >> start, but the results tree view is missing.
> >> >>
> >> >
> >> > I think in this case we should try to fail in a bit cleaner way
> >> >
> >>
> >> Done through bug  60583
> >> Still, not fully satisfied with solution as we catch a
> >> NoClassDefFoundError
> >> (I'll send a mail on this)
> >>
> >>
> >>
> >>- Or in response assertion
> >> >>>- Replace feature (partial)+ counting
> >> >>>
> >> >>> Maybe we can integrate before next release:
> >> >>>
> >> >>> - PR-247
> >> >>>
> >> >>
> >> If somebody can take it into account. I'm pausing for now.
> >>
> >>
> >>
> >> > - PR-246
> >> >>>
> >> >> Done with some changes.
> >> We can improve in the future by:
> >>
> >>- Using HttpComponents HttpAsyncClient
> >>- Make some properties configurable
> >>
> >>
> >> - PR-245
> >> >>>
> >> >> Done with some changes
> >>
> >> > - PR-237
> >> >>>
> >> >> Done
> >>
> >> >
> >> >>> And upgrade some dependencies:
> >> >>>
> >> >>> - jodd which has a lot of perf enhancements that we use in
> JMeter
> >> >>> (for
> >> >>> resources extractions)
> >> >>> - httpcomponents
> >> >>> - maybe more
> >> >>>
> >> >> Done
> >>
> >> I'd also like to commit :
> >>
> >>- https://bz.apache.org/bugzilla/show_bug.cgi?id=60514
> >>
> >>
> >> I would like to link  the converted pdf tutorials and maybe do a bit of
> >> >> minor tweaks to the look and feel of the web pages (less shadows).
> >> >>
> >> >> Should the sect-num number of the tutorials be continued from those
> in
> >> >> the usermanual section?
> >> >>
> >> >
> >> > I think so.
> >> >
> >> >
> >> >>> Besides, we did a lot of code changes related to sonar, let's
> release
> >> it.
> >> >>>
> >> >>> A last good thing is that we start to release more often.
> >> >>>
> >> >> +1
> >> >>
> >> >> Felix
> >> >>
> >> >>>
> >> >>>
> >> >>
> >> >
> >> >
> >> > --
> >> > Cordialement.
> >> > Philippe Mouawad.
> >> >
> >> >
> >> >
> >>
> >>
> >> --
> >> Cordialement.
> >> Philippe Mouawad.
> >>
> >
> >
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release JMeter 3.2 ?

[Philippe Mouawad]

Hello Maxime,
I merged some of your PR.
Did you have the opportunity to make tests of nightly build ?

Your feedback is welcome.
Thanks
Regards

On Fri, Jan 13, 2017 at 10:35 AM, Maxime Chassagneux <
maxime.chassagn...@gmail.com> wrote:

> Hi,
>
> Pls, could you consider to merge this PR too :
>
>  - PR-241 : Support variable for all JMS messages (bytes, object, ...) and
> sources (file, folder)
>  - PR-240 : Improves JMS component robustness
>
> Thanks .
>
> 2017-01-12 21:02 GMT+01:00 Philippe Mouawad :
>
> > On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
> > felix.schumac...@internetallee.de> wrote:
> >
> > > Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
> > >
> > >> Hello,
> > >> What do you think of releasing a 3.2 version ?
> > >>
> > > I think I said before, that I would like to release often :)
> > >
> > >>
> > >> I see following reasons:
> > >>
> > >> - There is a regression (See bug 60575)
> > >>
> > > My fix for 60575 needs tests and review as it changes the contract of
> the
> > > method getSendParameterValuesAsPostBody.
> > >
> > I reviewed it , it looks ok to me.
> > I'll double check.
> >
> > >
> > > It returned true if there were no parameters (and thus none with a
> name).
> > > (Or if getPostBodyRaw() is true)
> > >
> > > After the change it returns only true when there are parameters and
> none
> > > of those have a name. (Or if getPostBodyRaw() is true).
> > >
> >
> >
> >
> > >
> > > This method is used in POST and PUT as well, but I believe the change
> to
> > > be correct in both places. too.
> > >
> > > - We have 9 enhancements and 12  Bug fixes
> > >> - Some nice features (at least as a current user I find them
> > >> interesting
> > >> :-) ):
> > >>- More space in UI and simpler look
> > >>- Up to date Browser based on javafx
> > >>
> > > We might have to warn a bit more about the need for javafx (The default
> > > java for SUSE Leap42.2 seems to have no javafx). Without javafx JMeter
> > will
> > > start, but the results tree view is missing.
> > >
> >
> > I think in this case we should try to fail in a bit cleaner way
> >
> > >- Or in response assertion
> > >>- Replace feature (partial)+ counting
> > >>
> > >> Maybe we can integrate before next release:
> > >>
> > >> - PR-247
> > >> - PR-246
> > >> - PR-245
> > >> - PR-237
> > >>
> > >> And upgrade some dependencies:
> > >>
> > >> - jodd which has a lot of perf enhancements that we use in JMeter
> > (for
> > >> resources extractions)
> > >> - httpcomponents
> > >> - maybe more
> > >>
> > > I would like to link  the converted pdf tutorials and maybe do a bit of
> > > minor tweaks to the look and feel of the web pages (less shadows).
> > >
> > > Should the sect-num number of the tutorials be continued from those in
> > the
> > > usermanual section?
> > >
> >
> > I think so.
> >
> >
> > >> Besides, we did a lot of code changes related to sonar, let's release
> > it.
> > >>
> > >> A last good thing is that we start to release more often.
> > >>
> > > +1
> > >
> > > Felix
> > >
> > >>
> > >>
> > >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
>



-- 
Cordialement.
Philippe Mouawad.

Re: Release JMeter 3.2 ?

[Antonio Gomes Rodrigues]

Hi Philippe,

Thanks to your job

2017-01-15 23:20 GMT+01:00 Philippe Mouawad :

> On Thu, Jan 12, 2017 at 9:02 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
> >
> >
> > On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
> > felix.schumac...@internetallee.de> wrote:
> >
> >> Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
> >>
> >>> Hello,
> >>> What do you think of releasing a 3.2 version ?
> >>>
> >> I think I said before, that I would like to release often :)
> >>
> >>>
> >>> I see following reasons:
> >>>
> >>> - There is a regression (See bug 60575)
> >>>
> >> My fix for 60575 needs tests and review as it changes the contract of
> the
> >> method getSendParameterValuesAsPostBody.
> >>
> > I reviewed it , it looks ok to me.
> > I'll double check.
> >
> >>
> >> It returned true if there were no parameters (and thus none with a
> name).
> >> (Or if getPostBodyRaw() is true)
> >>
> >> After the change it returns only true when there are parameters and none
> >> of those have a name. (Or if getPostBodyRaw() is true).
> >>
> >
> >
> >
> >>
> >> This method is used in POST and PUT as well, but I believe the change to
> >> be correct in both places. too.
> >>
> >> - We have 9 enhancements and 12  Bug fixes
> >>> - Some nice features (at least as a current user I find them
> >>> interesting
> >>> :-) ):
> >>>- More space in UI and simpler look
> >>>- Up to date Browser based on javafx
> >>>
> >> We might have to warn a bit more about the need for javafx (The default
> >> java for SUSE Leap42.2 seems to have no javafx). Without javafx JMeter
> will
> >> start, but the results tree view is missing.
> >>
> >
> > I think in this case we should try to fail in a bit cleaner way
> >
>
> Done through bug  60583
> Still, not fully satisfied with solution as we catch a NoClassDefFoundError
> (I'll send a mail on this)
>
>
>
>- Or in response assertion
> >>>- Replace feature (partial)+ counting
> >>>
> >>> Maybe we can integrate before next release:
> >>>
> >>> - PR-247
> >>>
> >>
> If somebody can take it into account. I'm pausing for now.
>
>
>
> > - PR-246
> >>>
> >> Done with some changes.
> We can improve in the future by:
>
>- Using HttpComponents HttpAsyncClient
>- Make some properties configurable
>
>
> - PR-245
> >>>
> >> Done with some changes
>
> > - PR-237
> >>>
> >> Done
>
> >
> >>> And upgrade some dependencies:
> >>>
> >>> - jodd which has a lot of perf enhancements that we use in JMeter
> >>> (for
> >>> resources extractions)
> >>> - httpcomponents
> >>> - maybe more
> >>>
> >> Done
>
> I'd also like to commit :
>
>- https://bz.apache.org/bugzilla/show_bug.cgi?id=60514
>
>
> I would like to link  the converted pdf tutorials and maybe do a bit of
> >> minor tweaks to the look and feel of the web pages (less shadows).
> >>
> >> Should the sect-num number of the tutorials be continued from those in
> >> the usermanual section?
> >>
> >
> > I think so.
> >
> >
> >>> Besides, we did a lot of code changes related to sonar, let's release
> it.
> >>>
> >>> A last good thing is that we start to release more often.
> >>>
> >> +1
> >>
> >> Felix
> >>
> >>>
> >>>
> >>
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
> >
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>

Re: Release JMeter 3.2 ?

[Philippe Mouawad]

On Thu, Jan 12, 2017 at 9:02 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

>
>
> On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
> felix.schumac...@internetallee.de> wrote:
>
>> Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
>>
>>> Hello,
>>> What do you think of releasing a 3.2 version ?
>>>
>> I think I said before, that I would like to release often :)
>>
>>>
>>> I see following reasons:
>>>
>>> - There is a regression (See bug 60575)
>>>
>> My fix for 60575 needs tests and review as it changes the contract of the
>> method getSendParameterValuesAsPostBody.
>>
> I reviewed it , it looks ok to me.
> I'll double check.
>
>>
>> It returned true if there were no parameters (and thus none with a name).
>> (Or if getPostBodyRaw() is true)
>>
>> After the change it returns only true when there are parameters and none
>> of those have a name. (Or if getPostBodyRaw() is true).
>>
>
>
>
>>
>> This method is used in POST and PUT as well, but I believe the change to
>> be correct in both places. too.
>>
>> - We have 9 enhancements and 12  Bug fixes
>>> - Some nice features (at least as a current user I find them
>>> interesting
>>> :-) ):
>>>- More space in UI and simpler look
>>>- Up to date Browser based on javafx
>>>
>> We might have to warn a bit more about the need for javafx (The default
>> java for SUSE Leap42.2 seems to have no javafx). Without javafx JMeter will
>> start, but the results tree view is missing.
>>
>
> I think in this case we should try to fail in a bit cleaner way
>

Done through bug  60583
Still, not fully satisfied with solution as we catch a NoClassDefFoundError
(I'll send a mail on this)



   - Or in response assertion
>>>- Replace feature (partial)+ counting
>>>
>>> Maybe we can integrate before next release:
>>>
>>> - PR-247
>>>
>>
If somebody can take it into account. I'm pausing for now.



> - PR-246
>>>
>> Done with some changes.
We can improve in the future by:

   - Using HttpComponents HttpAsyncClient
   - Make some properties configurable


- PR-245
>>>
>> Done with some changes

> - PR-237
>>>
>> Done

>
>>> And upgrade some dependencies:
>>>
>>> - jodd which has a lot of perf enhancements that we use in JMeter
>>> (for
>>> resources extractions)
>>> - httpcomponents
>>> - maybe more
>>>
>> Done

I'd also like to commit :

   - https://bz.apache.org/bugzilla/show_bug.cgi?id=60514


I would like to link  the converted pdf tutorials and maybe do a bit of
>> minor tweaks to the look and feel of the web pages (less shadows).
>>
>> Should the sect-num number of the tutorials be continued from those in
>> the usermanual section?
>>
>
> I think so.
>
>
>>> Besides, we did a lot of code changes related to sonar, let's release it.
>>>
>>> A last good thing is that we start to release more often.
>>>
>> +1
>>
>> Felix
>>
>>>
>>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: VRT listener with JavaFX html view don't work with openjdk 8 [was Re: Release JMeter 3.2 ?]

[Milamber]

Hello Philippe,

Works better now the VRT is available and the HTML render works 
(fallback to old render)  (just 1 WARN line + stacktrace each time I had 
a VRT listener into the JMeter tree)


Thanks

Milamber

On 13/01/2017 13:51, Philippe Mouawad wrote:

Thanks.
Can you test new build which will be available in 10 minutes from now ?
Thanks

On Fri, Jan 13, 2017 at 1:56 PM, Milamber  wrote:


Done

https://bz.apache.org/bugzilla/show_bug.cgi?id=60583




On 13/01/2017 11:21, Philippe Mouawad wrote:


Hi Milamber,
Can you create a bugzilla for this ?
Thanks

On Fri, Jan 13, 2017 at 12:10 PM, Milamber  wrote:

 - Up to date Browser based on javafx

The listener View Result Tree don't appear in the menu if you start
JMeter
with openjdk8 (openjdk is the default JVM on Linux distros)

If you try to open a script JMX which include a VRT listerner a error box
display too.

Seems to be like a regression (on Linux platform)? Isn't possible to
fallback to old html render if the javafx class isn't found?


The error into jmeter.log:

2017/01/13 10:55:11 WARN  - jmeter.gui.util.MenuFactory: Configuration
error, probably corrupt or missing third party library(jar) ? Could not
create class:org.apache.jmeter.visualizers.ViewResultsFullVisualizer.
java.lang.NoClassDefFoundError: javafx/embed/swing/JFXPanel
java.lang.NoClassDefFoundError: javafx/embed/swing/JFXPanel
  at java.lang.Class.forName0(Native Method)
  at java.lang.Class.forName(Class.java:264)
  at org.apache.jmeter.visualizers.ViewResultsFullVisualizer.crea
teComboRender(ViewResultsFullVisualizer.java:340)
  at org.apache.jmeter.visualizers.ViewResultsFullVisualizer.crea
teLeftPanel(ViewResultsFullVisualizer.java:308)
  at org.apache.jmeter.visualizers.ViewResultsFullVisualizer.init
(ViewResultsFullVisualizer.java:229)
  at org.apache.jmeter.visualizers.ViewResultsFullVisualizer.(ViewResultsFullVisualizer.java:138)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ
e
Method)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance(Native
ConstructorAccessorImpl.java:62)
  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De
legatingConstructorAccessorImpl.java:45)
  at java.lang.reflect.Constructor.newInstance(Constructor.java:4
23)
  at java.lang.Class.newInstance(Class.java:442)
  at org.apache.jmeter.gui.util.MenuFactory.initializeMenus(MenuF
actory.java:497)
  at org.apache.jmeter.gui.util.MenuFactory.(MenuFactory.
java:168)
  at org.apache.jmeter.control.gui.WorkBenchGui.createPopupMenu(W
orkBenchGui.java:119)
  at org.apache.jmeter.gui.tree.JMeterTreeNode.createPopupMenu(JM
eterTreeNode.java:156)
  at org.apache.jmeter.gui.action.EditCommand.doAction(EditComman
d.java:46)
  at org.apache.jmeter.gui.action.ActionRouter.performAction(Acti
onRouter.java:80)
  at org.apache.jmeter.gui.action.ActionRouter.access$000(ActionR
outer.java:40)
  at org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter
.java:62)
  at java.awt.event.InvocationEvent.dispatch(InvocationEvent.
java:311)
  at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
  at java.awt.EventQueue.access$500(EventQueue.java:97)
  at java.awt.EventQueue$3.run(EventQueue.java:709)
  at java.awt.EventQueue$3.run(EventQueue.java:703)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.security.ProtectionDomain$JavaSecurityAccessImpl.doInte
rsectionPrivilege(ProtectionDomain.java:76)
  at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
  at org.GNOME.Accessibility.AtkWrapper$5.dispatchEvent(AtkWrappe
r.java:700)
  at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis
patchThread.java:201)
  at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat
chThread.java:116)
  at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDis
patchThread.java:105)
  at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.
java:101)
  at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.
java:93)
  at java.awt.EventDispatchThread.run(EventDispatchThread.java:82
)
Caused by: java.lang.ClassNotFoundException: javafx.embed.swing.JFXPanel
  at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
  ... 34 more



On 12/01/2017 19:39, Philippe Mouawad wrote:

Hello,

What do you think of releasing a 3.2 version ?

I see following reasons:

  - There is a regression (See bug 60575)
  - We have 9 enhancements and 12  Bug fixes
  - Some nice features (at least as a current user I find them
interesting
  :-) ):
 - More space in 

Re: VRT listener with JavaFX html view don't work with openjdk 8 [was Re: Release JMeter 3.2 ?]

[Milamber]

Done

https://bz.apache.org/bugzilla/show_bug.cgi?id=60583



On 13/01/2017 11:21, Philippe Mouawad wrote:

Hi Milamber,
Can you create a bugzilla for this ?
Thanks

On Fri, Jan 13, 2017 at 12:10 PM, Milamber  wrote:


- Up to date Browser based on javafx
The listener View Result Tree don't appear in the menu if you start JMeter
with openjdk8 (openjdk is the default JVM on Linux distros)

If you try to open a script JMX which include a VRT listerner a error box
display too.

Seems to be like a regression (on Linux platform)? Isn't possible to
fallback to old html render if the javafx class isn't found?


The error into jmeter.log:

2017/01/13 10:55:11 WARN  - jmeter.gui.util.MenuFactory: Configuration
error, probably corrupt or missing third party library(jar) ? Could not
create class:org.apache.jmeter.visualizers.ViewResultsFullVisualizer.
java.lang.NoClassDefFoundError: javafx/embed/swing/JFXPanel
java.lang.NoClassDefFoundError: javafx/embed/swing/JFXPanel
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:264)
 at org.apache.jmeter.visualizers.ViewResultsFullVisualizer.crea
teComboRender(ViewResultsFullVisualizer.java:340)
 at org.apache.jmeter.visualizers.ViewResultsFullVisualizer.crea
teLeftPanel(ViewResultsFullVisualizer.java:308)
 at org.apache.jmeter.visualizers.ViewResultsFullVisualizer.init
(ViewResultsFullVisualizer.java:229)
 at org.apache.jmeter.visualizers.ViewResultsFullVisualizer.(ViewResultsFullVisualizer.java:138)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(Native
ConstructorAccessorImpl.java:62)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De
legatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
 at java.lang.Class.newInstance(Class.java:442)
 at org.apache.jmeter.gui.util.MenuFactory.initializeMenus(MenuF
actory.java:497)
 at org.apache.jmeter.gui.util.MenuFactory.(MenuFactory.
java:168)
 at org.apache.jmeter.control.gui.WorkBenchGui.createPopupMenu(W
orkBenchGui.java:119)
 at org.apache.jmeter.gui.tree.JMeterTreeNode.createPopupMenu(JM
eterTreeNode.java:156)
 at org.apache.jmeter.gui.action.EditCommand.doAction(EditComman
d.java:46)
 at org.apache.jmeter.gui.action.ActionRouter.performAction(Acti
onRouter.java:80)
 at org.apache.jmeter.gui.action.ActionRouter.access$000(ActionR
outer.java:40)
 at org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter
.java:62)
 at java.awt.event.InvocationEvent.dispatch(InvocationEvent.
java:311)
 at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
 at java.awt.EventQueue.access$500(EventQueue.java:97)
 at java.awt.EventQueue$3.run(EventQueue.java:709)
 at java.awt.EventQueue$3.run(EventQueue.java:703)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.security.ProtectionDomain$JavaSecurityAccessImpl.doInte
rsectionPrivilege(ProtectionDomain.java:76)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
 at org.GNOME.Accessibility.AtkWrapper$5.dispatchEvent(AtkWrappe
r.java:700)
 at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis
patchThread.java:201)
 at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat
chThread.java:116)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDis
patchThread.java:105)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.
java:101)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.
java:93)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.lang.ClassNotFoundException: javafx.embed.swing.JFXPanel
 at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
 ... 34 more



On 12/01/2017 19:39, Philippe Mouawad wrote:


Hello,
What do you think of releasing a 3.2 version ?

I see following reasons:

 - There is a regression (See bug 60575)
 - We have 9 enhancements and 12  Bug fixes
 - Some nice features (at least as a current user I find them
interesting
 :-) ):
- More space in UI and simpler look
- Up to date Browser based on javafx
- Or in response assertion
- Replace feature (partial)+ counting

Maybe we can integrate before next release:

 - PR-247
 - PR-246
 - PR-245
 - PR-237

And upgrade some dependencies:

 - jodd which has a lot of perf enhancements that we use in JMeter (for
 resources extractions)
 - httpcomponents
 - maybe more

Besides, we did a lot of code changes 

VRT listener with JavaFX html view don't work with openjdk 8 [was Re: Release JMeter 3.2 ?]

[Milamber]

   - Up to date Browser based on javafx


The listener View Result Tree don't appear in the menu if you start 
JMeter with openjdk8 (openjdk is the default JVM on Linux distros)


If you try to open a script JMX which include a VRT listerner a error 
box display too.


Seems to be like a regression (on Linux platform)? Isn't possible to 
fallback to old html render if the javafx class isn't found?



The error into jmeter.log:

2017/01/13 10:55:11 WARN  - jmeter.gui.util.MenuFactory: Configuration 
error, probably corrupt or missing third party library(jar) ? Could not 
create class:org.apache.jmeter.visualizers.ViewResultsFullVisualizer. 
java.lang.NoClassDefFoundError: javafx/embed/swing/JFXPanel 
java.lang.NoClassDefFoundError: javafx/embed/swing/JFXPanel

at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at 
org.apache.jmeter.visualizers.ViewResultsFullVisualizer.createComboRender(ViewResultsFullVisualizer.java:340)
at 
org.apache.jmeter.visualizers.ViewResultsFullVisualizer.createLeftPanel(ViewResultsFullVisualizer.java:308)
at 
org.apache.jmeter.visualizers.ViewResultsFullVisualizer.init(ViewResultsFullVisualizer.java:229)
at 
org.apache.jmeter.visualizers.ViewResultsFullVisualizer.(ViewResultsFullVisualizer.java:138)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at 
org.apache.jmeter.gui.util.MenuFactory.initializeMenus(MenuFactory.java:497)
at 
org.apache.jmeter.gui.util.MenuFactory.(MenuFactory.java:168)
at 
org.apache.jmeter.control.gui.WorkBenchGui.createPopupMenu(WorkBenchGui.java:119)
at 
org.apache.jmeter.gui.tree.JMeterTreeNode.createPopupMenu(JMeterTreeNode.java:156)
at 
org.apache.jmeter.gui.action.EditCommand.doAction(EditCommand.java:46)
at 
org.apache.jmeter.gui.action.ActionRouter.performAction(ActionRouter.java:80)
at 
org.apache.jmeter.gui.action.ActionRouter.access$000(ActionRouter.java:40)
at 
org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter.java:62)
at 
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)

at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at 
org.GNOME.Accessibility.AtkWrapper$5.dispatchEvent(AtkWrapper.java:700)
at 
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at 
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at 
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at 
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)

at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.lang.ClassNotFoundException: javafx.embed.swing.JFXPanel
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 34 more



On 12/01/2017 19:39, Philippe Mouawad wrote:

Hello,
What do you think of releasing a 3.2 version ?

I see following reasons:

- There is a regression (See bug 60575)
- We have 9 enhancements and 12  Bug fixes
- Some nice features (at least as a current user I find them interesting
:-) ):
   - More space in UI and simpler look
   - Up to date Browser based on javafx
   - Or in response assertion
   - Replace feature (partial)+ counting

Maybe we can integrate before next release:

- PR-247
- PR-246
- PR-245
- PR-237

And upgrade some dependencies:

- jodd which has a lot of perf enhancements that we use in JMeter (for
resources extractions)
- httpcomponents
- maybe more

Besides, we did a lot of code changes related to sonar, let's release it.

A last good thing is that we start to release more often.

Re: Release JMeter 3.2 ?

[Maxime Chassagneux]

Hi,

Pls, could you consider to merge this PR too :

 - PR-241 : Support variable for all JMS messages (bytes, object, ...) and
sources (file, folder)
 - PR-240 : Improves JMS component robustness

Thanks .

2017-01-12 21:02 GMT+01:00 Philippe Mouawad :

> On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
> felix.schumac...@internetallee.de> wrote:
>
> > Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
> >
> >> Hello,
> >> What do you think of releasing a 3.2 version ?
> >>
> > I think I said before, that I would like to release often :)
> >
> >>
> >> I see following reasons:
> >>
> >> - There is a regression (See bug 60575)
> >>
> > My fix for 60575 needs tests and review as it changes the contract of the
> > method getSendParameterValuesAsPostBody.
> >
> I reviewed it , it looks ok to me.
> I'll double check.
>
> >
> > It returned true if there were no parameters (and thus none with a name).
> > (Or if getPostBodyRaw() is true)
> >
> > After the change it returns only true when there are parameters and none
> > of those have a name. (Or if getPostBodyRaw() is true).
> >
>
>
>
> >
> > This method is used in POST and PUT as well, but I believe the change to
> > be correct in both places. too.
> >
> > - We have 9 enhancements and 12  Bug fixes
> >> - Some nice features (at least as a current user I find them
> >> interesting
> >> :-) ):
> >>- More space in UI and simpler look
> >>- Up to date Browser based on javafx
> >>
> > We might have to warn a bit more about the need for javafx (The default
> > java for SUSE Leap42.2 seems to have no javafx). Without javafx JMeter
> will
> > start, but the results tree view is missing.
> >
>
> I think in this case we should try to fail in a bit cleaner way
>
> >- Or in response assertion
> >>- Replace feature (partial)+ counting
> >>
> >> Maybe we can integrate before next release:
> >>
> >> - PR-247
> >> - PR-246
> >> - PR-245
> >> - PR-237
> >>
> >> And upgrade some dependencies:
> >>
> >> - jodd which has a lot of perf enhancements that we use in JMeter
> (for
> >> resources extractions)
> >> - httpcomponents
> >> - maybe more
> >>
> > I would like to link  the converted pdf tutorials and maybe do a bit of
> > minor tweaks to the look and feel of the web pages (less shadows).
> >
> > Should the sect-num number of the tutorials be continued from those in
> the
> > usermanual section?
> >
>
> I think so.
>
>
> >> Besides, we did a lot of code changes related to sonar, let's release
> it.
> >>
> >> A last good thing is that we start to release more often.
> >>
> > +1
> >
> > Felix
> >
> >>
> >>
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>

Re: Release JMeter 3.2 ?

[Philippe Mouawad]

On Thu, Jan 12, 2017 at 8:55 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

> Am 12.01.2017 um 20:39 schrieb Philippe Mouawad:
>
>> Hello,
>> What do you think of releasing a 3.2 version ?
>>
> I think I said before, that I would like to release often :)
>
>>
>> I see following reasons:
>>
>> - There is a regression (See bug 60575)
>>
> My fix for 60575 needs tests and review as it changes the contract of the
> method getSendParameterValuesAsPostBody.
>
I reviewed it , it looks ok to me.
I'll double check.

>
> It returned true if there were no parameters (and thus none with a name).
> (Or if getPostBodyRaw() is true)
>
> After the change it returns only true when there are parameters and none
> of those have a name. (Or if getPostBodyRaw() is true).
>



>
> This method is used in POST and PUT as well, but I believe the change to
> be correct in both places. too.
>
> - We have 9 enhancements and 12  Bug fixes
>> - Some nice features (at least as a current user I find them
>> interesting
>> :-) ):
>>- More space in UI and simpler look
>>- Up to date Browser based on javafx
>>
> We might have to warn a bit more about the need for javafx (The default
> java for SUSE Leap42.2 seems to have no javafx). Without javafx JMeter will
> start, but the results tree view is missing.
>

I think in this case we should try to fail in a bit cleaner way

>- Or in response assertion
>>- Replace feature (partial)+ counting
>>
>> Maybe we can integrate before next release:
>>
>> - PR-247
>> - PR-246
>> - PR-245
>> - PR-237
>>
>> And upgrade some dependencies:
>>
>> - jodd which has a lot of perf enhancements that we use in JMeter (for
>> resources extractions)
>> - httpcomponents
>> - maybe more
>>
> I would like to link  the converted pdf tutorials and maybe do a bit of
> minor tweaks to the look and feel of the web pages (less shadows).
>
> Should the sect-num number of the tutorials be continued from those in the
> usermanual section?
>

I think so.


>> Besides, we did a lot of code changes related to sonar, let's release it.
>>
>> A last good thing is that we start to release more often.
>>
> +1
>
> Felix
>
>>
>>
>


-- 
Cordialement.
Philippe Mouawad.