RE: enhancement to jmeter.sh startup script

[James Liang]

https://issues.apache.org/bugzilla/show_bug.cgi?id=55994

Regarding all shells, the top of the jmeter.sh script already specified
#! /bin/sh

As such the script can be call by within unix shell.


Thanks,
James Liang


-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: Saturday, January 11, 2014 4:17 PM
To: dev@jmeter.apache.org
Subject: Re: enhancement to jmeter.sh startup script

On 12 January 2014 00:00, James Liang  wrote:
> Hi guys,
>
> The bin/jmeter.sh script will fail to launch if it is called via symlink or 
> called from outside of bin.
>
> Adding the following snippet of script will resolve the true path, cd to it, 
> and then start jmeter.

Thanks - could you add that to a Bugzilla issue?

Also, does that fix work for all shells?
It looks like it might be specific to bash.

> --
>
> # resolve the true full path (e.g. called from outside of bin, called 
> via symlinks, and etc.) SOURCE="${BASH_SOURCE[0]}"
> while [ -h "$SOURCE" ]; do # resolve $SOURCE until the file is no longer a 
> symlink
>   DIR="$( cd -P "$( dirname "$SOURCE" )" && pwd )"
>   SOURCE="$(readlink "$SOURCE")"
>   [[ $SOURCE != /* ]] && SOURCE="$DIR/$SOURCE" # if $SOURCE was a 
> relative symlink, we need to resolve it relative to the path where the 
> symlink file was located done DIR="$( cd -P "$( dirname "$SOURCE" )" && pwd )"
>
> echo "start jmeter.sh from $DIR"
> cd "$DIR"
>
> # the rest of the jmeter.sh scripts
> # i.e.  JMETER_OPTS="" ...
>
>
>
> Thanks,
> James Liang
>
>

Jenkins build is back to normal : JMeter-trunk #3644

[Apache Jenkins Server]

See 

Build failed in Jenkins: JMeter-trunk #3643

[Apache Jenkins Server]

See 

Changes:

[pmouawad] Bug 52013 - Test Script Recorder's Child View Results Tree does not 
take into account Test Script Recorder excluded/included URLs
Set "Notify Child Listeners of filtered samplers" default value to true as per 
sebb last comment
Bugzilla Id: 52013

--
[...truncated 783 lines...]
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/building.html
   [anakia] Input:  changes.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/changes.html
   [anakia] Input:  changes_history.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/changes_history.html
   [anakia] Input:  download_jmeter.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/download_jmeter.html
   [anakia] Input:  index.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/index.html
   [anakia] Input:  issues.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/issues.html
   [anakia] Input:  jmeter_irc.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/jmeter_irc.html
   [anakia] Input:  localising/index.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/localising/index.html
   [anakia] Input:  mail.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/mail.html
   [anakia] Input:  mail2.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/mail2.html
   [anakia] Input:  nightly.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/nightly.html
   [anakia] Input:  svnindex.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/svnindex.html
   [anakia] Input:  usermanual/best-practices.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/best-practices.html
   [anakia] Input:  usermanual/boss.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/boss.html
   [anakia] Input:  usermanual/build-adv-web-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-adv-web-test-plan.html
   [anakia] Input:  usermanual/build-db-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-db-test-plan.html
   [anakia] Input:  usermanual/build-ftp-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-ftp-test-plan.html
   [anakia] Input:  usermanual/build-jms-point-to-point-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-jms-point-to-point-test-plan.html
   [anakia] Input:  usermanual/build-jms-topic-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-jms-topic-test-plan.html
   [anakia] Input:  usermanual/build-ldap-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-ldap-test-plan.html
   [anakia] Input:  usermanual/build-ldapext-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-ldapext-test-plan.html
   [anakia] Input:  usermanual/build-monitor-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-monitor-test-plan.html
   [anakia] Input:  usermanual/build-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-test-plan.html
   [anakia] Input:  usermanual/build-web-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-web-test-plan.html
   [anakia] Input:  usermanual/build-ws-test-plan.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/build-ws-test-plan.html
   [anakia] Input:  usermanual/component_reference.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/component_reference.html
   [anakia] Input:  usermanual/functions.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/functions.html
   [anakia] Input:  usermanual/get-started.xml
   [anakia] Output: 
/home/hudson/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/get-started.html
   [anakia] Input:  usermanual/g

Re: bug and fix for ProxyControl.deliverSampler() method

[sebb]

On 12 January 2014 14:58, Philippe Mouawad  wrote:
> Hello,
> Enhancement implemented with addition of a new setting in Recorder:
> - Notify Child Listeners of filtered samplers (unchecked by default)

I think it's wrong to change the default here, even if it is
documented as an incompatible change.

> Regards
>
>
> On Sun, Jan 12, 2014 at 9:27 AM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>> Hello,
>> A bugzilla already exists:
>> - https://issues.apache.org/bugzilla/show_bug.cgi?id=52013
>>
>> Regards
>> Philippe
>>
>>
>> On Sunday, January 12, 2014, sebb wrote:
>>
>>> Bug reports and enhancement requests are much easier to keep track of
>>> if they are recorded in the JMeter issue tracking system, i.e.
>>> Bugzilla.
>>>
>>> Could you please create yourself a login and upload the details there?
>>> Thanks!
>>>
>>>
>>> On 12 January 2014 00:35, James Liang  wrote:
>>> > Bug:
>>> >
>>> >
>>> >
>>> > The Test Script Recorder (proxy) supports filtering of url patterns
>>> before
>>> > sending the http requests to the Recording Controller.  Just to be
>>> clear,
>>> > this part works.  However, if we add a View Results Tree element to the
>>> Test
>>> > Script Recorder, the View Results Tree captures all calls and completely
>>> > ignores the filtering rules.
>>> >
>>> >
>>> >
>>> > As a result the calls captured by Recording Controller is in consistent
>>> with
>>> > the View Results Tree of the recorder.  This complicates the
>>> reconciliation
>>> > of the captured tests and the recorded result tree.  Furthermore, the
>>> filter
>>> > is use to filter out resources (e.g. jpg, css, etc.) which are quite
>>> > numerous.  The test script recorder would be easier to use and more
>>> > consistent if the Test Script Recorder honors the filter rule when it
>>> > forwards the result to the View Results Tree.  In other words, the Test
>>> > Scripts Recorder should send the same output to both the Recording
>>> > Controller and View Results Tree.
>>> >
>>> >
>>> >
>>> > Fix:
>>> >
>>> > ProxyControl.java
>>> >
>>> >
>>> >
>>> > method:
>>> >
>>> > public synchronized void deliverSampler(final HTTPSamplerBase sampler,
>>> final
>>> > TestElement[] subConfigs, final SampleResult result)
>>> >
>>> >
>>> >
>>> > changes:
>>> >
>>> >
>>> >
>>> > move line 545 to after 536 (before 537) so that the filter rule applies
>>> to
>>> > the notification.
>>> >
>>> >
>>> >
>>> > The code of the line to move is:
>>> >
>>> > notifySampleListeners(new SampleEvent(result, "WorkBench")); // TODO -
>>> is
>>> > this the correct threadgroup name?
>>> >
>>> >
>>> >
>>> > I’ve attached the corrected java file.  The fix is based on the v2_10
>>> src
>>> > tree.
>>> >
>>> >
>>> http://svn.apache.org/viewvc/jmeter/tags/v2_10/src/protocol/http/org/apache/jmeter/protocol/http/proxy/ProxyControl.java?revision=1533926&view=markup
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Thanks,
>>> >
>>> > James Liang
>>> >
>>> >
>>> >
>>> >
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Jenkins build is back to normal : JMeter-trunk #3641

[Apache Jenkins Server]

See 

Re: bug and fix for ProxyControl.deliverSampler() method

[Philippe Mouawad]

Hello,
Enhancement implemented with addition of a new setting in Recorder:
- Notify Child Listeners of filtered samplers (unchecked by default)

Regards


On Sun, Jan 12, 2014 at 9:27 AM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> Hello,
> A bugzilla already exists:
> - https://issues.apache.org/bugzilla/show_bug.cgi?id=52013
>
> Regards
> Philippe
>
>
> On Sunday, January 12, 2014, sebb wrote:
>
>> Bug reports and enhancement requests are much easier to keep track of
>> if they are recorded in the JMeter issue tracking system, i.e.
>> Bugzilla.
>>
>> Could you please create yourself a login and upload the details there?
>> Thanks!
>>
>>
>> On 12 January 2014 00:35, James Liang  wrote:
>> > Bug:
>> >
>> >
>> >
>> > The Test Script Recorder (proxy) supports filtering of url patterns
>> before
>> > sending the http requests to the Recording Controller.  Just to be
>> clear,
>> > this part works.  However, if we add a View Results Tree element to the
>> Test
>> > Script Recorder, the View Results Tree captures all calls and completely
>> > ignores the filtering rules.
>> >
>> >
>> >
>> > As a result the calls captured by Recording Controller is in consistent
>> with
>> > the View Results Tree of the recorder.  This complicates the
>> reconciliation
>> > of the captured tests and the recorded result tree.  Furthermore, the
>> filter
>> > is use to filter out resources (e.g. jpg, css, etc.) which are quite
>> > numerous.  The test script recorder would be easier to use and more
>> > consistent if the Test Script Recorder honors the filter rule when it
>> > forwards the result to the View Results Tree.  In other words, the Test
>> > Scripts Recorder should send the same output to both the Recording
>> > Controller and View Results Tree.
>> >
>> >
>> >
>> > Fix:
>> >
>> > ProxyControl.java
>> >
>> >
>> >
>> > method:
>> >
>> > public synchronized void deliverSampler(final HTTPSamplerBase sampler,
>> final
>> > TestElement[] subConfigs, final SampleResult result)
>> >
>> >
>> >
>> > changes:
>> >
>> >
>> >
>> > move line 545 to after 536 (before 537) so that the filter rule applies
>> to
>> > the notification.
>> >
>> >
>> >
>> > The code of the line to move is:
>> >
>> > notifySampleListeners(new SampleEvent(result, "WorkBench")); // TODO -
>> is
>> > this the correct threadgroup name?
>> >
>> >
>> >
>> > I’ve attached the corrected java file.  The fix is based on the v2_10
>> src
>> > tree.
>> >
>> >
>> http://svn.apache.org/viewvc/jmeter/tags/v2_10/src/protocol/http/org/apache/jmeter/protocol/http/proxy/ProxyControl.java?revision=1533926&view=markup
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Thanks,
>> >
>> > James Liang
>> >
>> >
>> >
>> >
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

buildbot success in ASF Buildbot on jmeter-trunk

[buildbot]

The Buildbot has detected a restored build on builder jmeter-trunk while 
building ASF Buildbot.
Full details are available at:
 http://ci.apache.org/builders/jmeter-trunk/builds/2428

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: hemera_ubuntu

Build Reason: scheduler
Build Source Stamp: [branch jmeter/trunk] 1557539
Blamelist: sebb

Build succeeded!

sincerely,
 -The Buildbot

Re: Special Vote (2.10) : publish mongodb jar on Maven Central for JMeter 2.10

[sebb]

On 12 January 2014 09:12, Milamber  wrote:
> Hello,
>
> This a special vote for republish all the JMeter 2.10 jars on Maven central,
> including the missing mongodb jar file.
> (see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )
>
> All jars come directly from the original release directory (I have been the
> release manager, and I don't removed the release directory on my machine).
> I've only modify the build.xml to add the mongodb jar on maven_upload task
> (perhaps I need to commit this changes on 2.10 branch?)
>
> You can check the jars in staging directory on Nexus:
>
> https://repository.apache.org/content/repositories/orgapachejmeter-1000/org/apache/jmeter/
>
> You can vote:
>
> [X ] +1  I support this update (binding)
> [  ] +0  I am OK with this update
> [  ] -0   OK, but
> [  ] -1   I do not support this  update (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 this jars files on
> Nexus, to allow a publish on Maven central.
>
> Thanks,
> Milamber
>

Re: Special Vote (2.11) : publish mongodb jar on Maven Central for JMeter 2.11

[sebb]

On 12 January 2014 09:27, Milamber  wrote:
> Hello,
>
> This a special vote for republish all the JMeter 2.11 jars on Maven central,
> including the missing mongodb jar file.
> (see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )
>
> All jars come directly from the original release directory (I have been the
> release manager, and I don't removed the release directory on my machine).
> I've only modify the build.xml to add the mongodb jar on maven_upload task
> (perhaps I need to commit this changes on 2.11 branch?)
>
> You can check the jars in staging directory on Nexus:
>
> https://repository.apache.org/content/repositories/orgapachejmeter-1001/org/apache/jmeter/
>
> You can vote:
>
> [X] +1  I support this update
> [  ] +0  I am OK with this update
> [  ] -0   OK, but
> [  ] -1   I do not support this  update (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 this jars files on
> Nexus, to allow a publish on Maven central.
>
> Thanks,
> Milamber
>

Build failed in Jenkins: JMeter-trunk #3640

[Apache Jenkins Server]

See 

--
[...truncated 4096 lines...]
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/intro.html
   [anakia] Input:  usermanual/ldapanswer_xml.xml
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/ldapanswer_xml.html
   [anakia] Input:  usermanual/ldapops_tutor.xml
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/ldapops_tutor.html
   [anakia] Input:  usermanual/listeners.xml
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/listeners.html
   [anakia] Input:  usermanual/regular_expressions.xml
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/regular_expressions.html
   [anakia] Input:  usermanual/remote-test.xml
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/remote-test.html
   [anakia] Input:  usermanual/test_plan.xml
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/test_plan.html
 [echo] Fixing EOL
 [echo] Removing unnecessary  tags
 [echo] Copying files
 [copy] Copying 16 files to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/demos
 [copy] Copying 5 files to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual
 [copy] Copying 1 file to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/extending

pack-nightly:

_pack-binaries:
[mkdir] Created dir: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist
  [tar] Building tar: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_bin.tar
 [gzip] Building: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_bin.tgz
   [delete] Deleting: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_bin.tar
  [zip] Building zip: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_bin.zip

_pack-libraries:
  [tar] Building tar: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_lib.tar
 [gzip] Building: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_lib.tgz
   [delete] Deleting: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_lib.tar
  [zip] Building zip: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_lib.zip

_pack-source:
  [tar] Building tar: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_src.tar
 [gzip] Building: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_src.tgz
   [delete] Deleting: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_src.tar
  [zip] Building zip: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/dist/apache-jmeter-r1556932_src.zip

nightly:

compile-tests:
[mkdir] Created dir: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/build/test
[javac] Compiling 100 source files to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/build/test

_test:
 [echo] 
 [echo]gump.run = false
 [echo]java.awt.headless = true
 [echo]test.headless = true
 [echo]user.dir = /x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk
 [echo]basedir = /x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk
 [echo]test dir = build/test
 [echo]test dir gump = build/test
 [echo]testsaveservice.saveout = ${testsaveservice.saveout}
 [echo]test.encoding = UTF-8
 [echo]
 [java] Setting JMeterHome: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk
 [java] Setting up logging props using file: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/bin/testfiles/jmetertest.properties
 [java] Using initializeProperties() from org.apache.jmeter.util.JMeterUtils
 [java] Setting up initial properties using: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/bin/testfiles/jmetertest.properties
 [java] Initializing Properties: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/bin/testfiles/jmetertest.properties
 [java] JMeterVersion=r1556932
 [java] java.version=1.6.0_45
 [java] java.home=/x1/jenkins/tools/java/jdk1.6.0_45-32/jre
 [java] file.encoding=UTF-8
 [java] default encoding=UTF-8
 [java] user.dir=/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/bin
 [java] Locale=en_US
 [java] os.name=Linux
 [java] os.version=3.2.0-57-generic
 [java] +++
 [java] java.awt.headless=true
 [java] java.awt.graphicsenv=sun.awt.X11GraphicsE

Re: Special Vote (2.11) : publish mongodb jar on Maven Central for JMeter 2.11

[Rainer Jung]

On 12.01.2014 10:27, Milamber wrote:
> Hello,
> 
> This a special vote for republish all the JMeter 2.11 jars on Maven
> central, including the missing mongodb jar file.
> (see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )
> 
> All jars come directly from the original release directory (I have been
> the release manager, and I don't removed the release directory on my
> machine).
> I've only modify the build.xml to add the mongodb jar on maven_upload
> task (perhaps I need to commit this changes on 2.11 branch?)
> 
> You can check the jars in staging directory on Nexus:
> 
> https://repository.apache.org/content/repositories/orgapachejmeter-1001/org/apache/jmeter/
> 
> 
> You can vote:
> 
> [XX] +1  I support this update
> [  ] +0  I am OK with this update
> [  ] -0   OK, but
> [  ] -1   I do not support this  update (please indicate why)
> 
> The vote will remain open for at least 72 hours.
> 
> The PMC members please indicate the mention "(binding)" with your vote.

+1 (binding)

Compared with original repos (same types of changes as for 2.10):

- mongodb added
- index.html some formal changes, probably due to a nexus change
- maven-metadata.xml changed  field
- maven-metadata.xml.md5 and maven-metadata.xml.sha1 changed accordingly

Thanks and regards,

Rainer

Re: Special Vote (2.10) : publish mongodb jar on Maven Central for JMeter 2.10

[Rainer Jung]

On 12.01.2014 10:12, Milamber wrote:
> Hello,
> 
> This a special vote for republish all the JMeter 2.10 jars on Maven
> central, including the missing mongodb jar file.
> (see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )
> 
> All jars come directly from the original release directory (I have been
> the release manager, and I don't removed the release directory on my
> machine).
> I've only modify the build.xml to add the mongodb jar on maven_upload
> task (perhaps I need to commit this changes on 2.10 branch?)
> 
> You can check the jars in staging directory on Nexus:
> 
> https://repository.apache.org/content/repositories/orgapachejmeter-1000/org/apache/jmeter/
> 
> 
> You can vote:
> 
> [XX] +1  I support this update
> [  ] +0  I am OK with this update
> [  ] -0   OK, but
> [  ] -1   I do not support this  update (please indicate why)
> 
> The vote will remain open for at least 72 hours.
> 
> The PMC members please indicate the mention "(binding)" with your vote.

+1 (binding)

Compared with original repos:

- mongodb added
- index.html some formal changes, probably due to a nexus change
- maven-metadata.xml changed  field
- maven-metadata.xml.md5 and maven-metadata.xml.sha1 changed accordingly

Thanks and regards,

Rainer

Re: Special Vote (2.10) : publish mongodb jar on Maven Central for JMeter 2.10

[Milamber]

Le 12/01/2014 09:17, Philippe Mouawad a ecrit :

The vote will remain open for at least 72 hours.

Do we really need to wait 72 hours ? As it is just jars upload ?

Yes it's trivial, but with 72 hours, we are sure that the max of people 
have seen the vote announce and can vote or send feedback.


Milamber

Re: Special Vote (2.11) : publish mongodb jar on Maven Central for JMeter 2.11

[NaveenKumar Namachivayam]

+1


On Sun, Jan 12, 2014 at 2:57 PM, Milamber  wrote:

> Hello,
>
> This a special vote for republish all the JMeter 2.11 jars on Maven
> central, including the missing mongodb jar file.
> (see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )
>
> All jars come directly from the original release directory (I have been
> the release manager, and I don't removed the release directory on my
> machine).
> I've only modify the build.xml to add the mongodb jar on maven_upload task
> (perhaps I need to commit this changes on 2.11 branch?)
>
> You can check the jars in staging directory on Nexus:
>
> https://repository.apache.org/content/repositories/
> orgapachejmeter-1001/org/apache/jmeter/
>
> You can vote:
>
> [  ] +1  I support this update
> [  ] +0  I am OK with this update
> [  ] -0   OK, but
> [  ] -1   I do not support this  update (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 this jars files on
> Nexus, to allow a publish on Maven central.
>
> Thanks,
> Milamber
>
>


-- 
Thank you,

Regards,
NaveenKumar N
Visit www.QAInsights.com and www.Testifications.com and www.MyTechCube.com

Re: ApacheJMeter_mongodb is missing from maven central

[Mark Collin]

I have now :)

Thanks for keeping me up to date.

On 12 Jan 2014, at 09:33, Philippe Mouawad  wrote:

> Hello,
> You probably have seen vote started, if not ETA should be around 72 hours +
> few more hours for ending operations.
> 
> Thanks to RM milamber !
> 
> Regards
> 
> On Saturday, January 11, 2014, Mark Collin wrote:
> 
>> Do you have a rough ETA for getting the 2.10 and 2.11 ApacheJMeter_mongodb
>> jars up in maven central?
>> 
>> I have a new release of the jmeter-maven-plugin ready to go and I’m trying
>> to decide whether to wait for the jar to be in maven central, or just mark
>> the missing jar as a known problem with a workaround for when it is
>> available.
>> 
>> 
>> On 8 Jan 2014, at 00:22, sebb > wrote:
>> 
>>> On 8 January 2014 00:09, Milamber >
>> wrote:
 Hello,
 
 Thanks for report. I've fixed this for next release.
 
 @Sebb, what is the best way to upload the mongo maven package ?
>>> 
>>> I don't know if it's possible to add extra jars to an existing release or
>>> not.
>>> I suggest you ask on the Maven user list.
>>> 
>>> Note: since the pom is source, we probably ought to vote on the updates

Re: ApacheJMeter_mongodb is missing from maven central

[Philippe Mouawad]

Hello,
You probably have seen vote started, if not ETA should be around 72 hours +
few more hours for ending operations.

Thanks to RM milamber !

Regards

On Saturday, January 11, 2014, Mark Collin wrote:

> Do you have a rough ETA for getting the 2.10 and 2.11 ApacheJMeter_mongodb
> jars up in maven central?
>
> I have a new release of the jmeter-maven-plugin ready to go and I’m trying
> to decide whether to wait for the jar to be in maven central, or just mark
> the missing jar as a known problem with a workaround for when it is
> available.
>
>
> On 8 Jan 2014, at 00:22, sebb > wrote:
>
> > On 8 January 2014 00:09, Milamber >
> wrote:
> >> Hello,
> >>
> >> Thanks for report. I've fixed this for next release.
> >>
> >> @Sebb, what is the best way to upload the mongo maven package ?
> >
> > I don't know if it's possible to add extra jars to an existing release or
> > not.
> > I suggest you ask on the Maven user list.
> >
> > Note: since the pom is source, we probably ought to vote on the updates.
> > Also we should ensure that the jars in the release are copies of the
> > ones in the binary archive, rather than rebuilds.
> >
> > Since all write access to Maven Central is via Nexus, and Nexus can
> > only hold one staging area for each GA pair, this will have to be done
> > in two stages.
> > i.e. upload 2.10 (somehow), vote, promote
> > then repeat for 2.11
> >
> >> Milamber
> >>
> >>
> >> Le 07/01/2014 10:54, Mark Collin a ecrit :
> >>
> >>> I’ve logged this as:
> >>>
> >>> https://issues.apache.org/bugzilla/show_bug.cgi?id=55965
> >>>
> >>>
>  On 7 Jan 2014, at 10:47, Mark Collin 
>  
> >
>  wrote:
> 
>  Just been going through the dependencies in maven central today and
> > I’ve
>  noticed that ApacheJMeter_mongodb is missing for 2.10 and 2.11.
> 
>  Can these be uploaded?
> >>>
> >>>
> >>
>
>

-- 
Cordialement.
Philippe Mouawad.

Re: Special Vote (2.11) : publish mongodb jar on Maven Central for JMeter 2.11

[Philippe Mouawad]

On Sunday, January 12, 2014, Milamber wrote:

> Hello,
>
> This a special vote for republish all the JMeter 2.11 jars on Maven
> central, including the missing mongodb jar file.
> (see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )
>
> All jars come directly from the original release directory (I have been
> the release manager, and I don't removed the release directory on my
> machine).
> I've only modify the build.xml to add the mongodb jar on maven_upload task
> (perhaps I need to commit this changes on 2.11 branch?)
>
> You can check the jars in staging directory on Nexus:
>
> https://repository.apache.org/content/repositories/
> orgapachejmeter-1001/org/apache/jmeter/
>
> You can vote:
>
> [  ] +1  I support this update
> [  ] +0  I am OK with this update
> [  ] -0   OK, but
> [  ] -1   I do not support this  update (please indicate why)
>
>
 +1  I support this update (binding)

> 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 this jars files on
> Nexus, to allow a publish on Maven central.
>
> Thanks,
> Milamber
>
>

-- 
Cordialement.
Philippe Mouawad.

Special Vote (2.11) : publish mongodb jar on Maven Central for JMeter 2.11

[Milamber]

Hello,

This a special vote for republish all the JMeter 2.11 jars on Maven 
central, including the missing mongodb jar file.

(see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )

All jars come directly from the original release directory (I have been 
the release manager, and I don't removed the release directory on my 
machine).
I've only modify the build.xml to add the mongodb jar on maven_upload 
task (perhaps I need to commit this changes on 2.11 branch?)


You can check the jars in staging directory on Nexus:

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

You can vote:

[  ] +1  I support this update
[  ] +0  I am OK with this update
[  ] -0   OK, but
[  ] -1   I do not support this  update (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 this jars files on 
Nexus, to allow a publish on Maven central.


Thanks,
Milamber

Re: Special Vote (2.10) : publish mongodb jar on Maven Central for JMeter 2.10

[Philippe Mouawad]

On Sunday, January 12, 2014, Milamber wrote:

> Hello,
>
> This a special vote for republish all the JMeter 2.10 jars on Maven
> central, including the missing mongodb jar file.
> (see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )
>
> All jars come directly from the original release directory (I have been
> the release manager, and I don't removed the release directory on my
> machine).
> I've only modify the build.xml to add the mongodb jar on maven_upload task
> (perhaps I need to commit this changes on 2.10 branch?)
>
> You can check the jars in staging directory on Nexus:
>
> https://repository.apache.org/content/repositories/
> orgapachejmeter-1000/org/apache/jmeter/
>
> You can vote:
>
> [  ] +1  I support this update


+1  I support this update


> [  ] +0  I am OK with this update
> [  ] -0   OK, but
> [  ] -1   I do not support this  update (please indicate why)
>
> The vote will remain open for at least 72 hours.


Do we really need to wait 72 hours ? As it is just jars upload ?

>
> The PMC members please indicate the mention "(binding)" with your vote.
>
>
> Note: If the vote passes, the intention is to release this jars files on
> Nexus, to allow a publish on Maven central.
>
> Thanks,
> Milamber
>
>

-- 
Cordialement.
Philippe Mouawad.

Special Vote (2.10) : publish mongodb jar on Maven Central for JMeter 2.10

[Milamber]

Hello,

This a special vote for republish all the JMeter 2.10 jars on Maven 
central, including the missing mongodb jar file.

(see https://issues.apache.org/bugzilla/show_bug.cgi?id=55965 )

All jars come directly from the original release directory (I have been 
the release manager, and I don't removed the release directory on my 
machine).
I've only modify the build.xml to add the mongodb jar on maven_upload 
task (perhaps I need to commit this changes on 2.10 branch?)


You can check the jars in staging directory on Nexus:

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

You can vote:

[  ] +1  I support this update
[  ] +0  I am OK with this update
[  ] -0   OK, but
[  ] -1   I do not support this  update (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 this jars files on 
Nexus, to allow a publish on Maven central.


Thanks,
Milamber

Re: bug and fix for ProxyControl.deliverSampler() method

[Philippe Mouawad]

Hello,
A bugzilla already exists:
- https://issues.apache.org/bugzilla/show_bug.cgi?id=52013

Regards
Philippe

On Sunday, January 12, 2014, sebb wrote:

> Bug reports and enhancement requests are much easier to keep track of
> if they are recorded in the JMeter issue tracking system, i.e.
> Bugzilla.
>
> Could you please create yourself a login and upload the details there?
> Thanks!
>
>
> On 12 January 2014 00:35, James Liang >
> wrote:
> > Bug:
> >
> >
> >
> > The Test Script Recorder (proxy) supports filtering of url patterns
> before
> > sending the http requests to the Recording Controller.  Just to be clear,
> > this part works.  However, if we add a View Results Tree element to the
> Test
> > Script Recorder, the View Results Tree captures all calls and completely
> > ignores the filtering rules.
> >
> >
> >
> > As a result the calls captured by Recording Controller is in consistent
> with
> > the View Results Tree of the recorder.  This complicates the
> reconciliation
> > of the captured tests and the recorded result tree.  Furthermore, the
> filter
> > is use to filter out resources (e.g. jpg, css, etc.) which are quite
> > numerous.  The test script recorder would be easier to use and more
> > consistent if the Test Script Recorder honors the filter rule when it
> > forwards the result to the View Results Tree.  In other words, the Test
> > Scripts Recorder should send the same output to both the Recording
> > Controller and View Results Tree.
> >
> >
> >
> > Fix:
> >
> > ProxyControl.java
> >
> >
> >
> > method:
> >
> > public synchronized void deliverSampler(final HTTPSamplerBase sampler,
> final
> > TestElement[] subConfigs, final SampleResult result)
> >
> >
> >
> > changes:
> >
> >
> >
> > move line 545 to after 536 (before 537) so that the filter rule applies
> to
> > the notification.
> >
> >
> >
> > The code of the line to move is:
> >
> > notifySampleListeners(new SampleEvent(result, "WorkBench")); // TODO - is
> > this the correct threadgroup name?
> >
> >
> >
> > I’ve attached the corrected java file.  The fix is based on the v2_10 src
> > tree.
> >
> >
> http://svn.apache.org/viewvc/jmeter/tags/v2_10/src/protocol/http/org/apache/jmeter/protocol/http/proxy/ProxyControl.java?revision=1533926&view=markup
> >
> >
> >
> >
> >
> >
> >
> > Thanks,
> >
> > James Liang
> >
> >
> >
> >
>


-- 
Cordialement.
Philippe Mouawad.