Unfortunately JMeter 2.3.3 introduced some new bugs. I have therefore created 2.3.4RC3 which is basically a bug-fix release. [Tags RC1 and RC2 were abandoned, as I forgot to change all the versions]
Archives/hashes/sigs and RAT report: http://people.apache.org/~sebb/jmeter-2.3.4RC3/dist MD5 hashes of archives for this vote: cef24a84bcfc814f9b5b1f7b6a8f389f *jakarta-jmeter-2.3.4.tgz dc056ac75b43859b72fca9b413f7619d *jakarta-jmeter-2.3.4.zip 1df877d81fee18bdff0bf56eb8094f3b *jakarta-jmeter-2.3.4_src.tgz f1365878508bfad1d3c4e7a7605ff566 *jakarta-jmeter-2.3.4_src.zip Site Docs are here: http://people.apache.org/~sebb/jmeter-2.3.4RC3/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_3_4_RC3 (r785646) Keys are here: http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ also http://www.apache.org/dist/jakarta/jmeter/KEYS N.B. To rebuild JMeter or run the unit tests, you need to unpack both the binary and source archives into the same directory structure. This is because the library files are only included in the binary archive. To create the jars and test JMeter: "ant package test". Note that there is a bug in Java on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: [java] WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number This does not affect JMeter operation. All feedback (and votes!) 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. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Here's my: +1 S/// --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org
