On 10 August 2011 20:07, Milamber <[email protected]> wrote: > > > Le 10/08/2011 17:06, sebb a ecrit : >> On 9 August 2011 16:46, Milamber <[email protected]> wrote: >> >>> >>> Le 09/08/2011 14:58, sebb a ecrit : >>> >>>> Sorry, but I think the JMeterVersion changes need a bit more work. >>>> I did not realise all the consequences of trying to align the SVN tag >>>> with the source archive. >>>> I think the current build.xml does not work well for non-SVN builds. >>>> >>>> >>> Yes. I've added 2 options on build.xml to permit build for non-svn >>> http://svn.apache.org/viewvc?rev=1154787&view=rev >>> Perhaps, it is not very elegant, but works. >>> >> The problem is that the build generates a version which is misleading. >> I need to work on the problem further. >> >> But anyway, I've just discovered a packaging problem which means that >> RC2 cannot be released as is. >> >> bin/hc.properties is missing from the source archive, and there are >> some other problems which I'm still investigating. >> >> So -1 from me for RC2. >> Sorry. >> > > Ok, no problem for a new RC. You are right, and I would like too a good > quality for this new release. > > I will cancel the RC2 tag.
I think I have fixed all the problems now, if you want to try an RC3. There's no need to run touch_version anymore, as the revision number is now taken from the manifest. As far as I can tell, there's now no need to use the new build svn 'skip' options, but I left them in just in case. So the procedure should be as it was originally. > Milamber > >> [BTW, it usually takes me at least 3 goes to get it right!] >> >> >>> Milamber >>> >>> >>>> What do we need the build script to provide? At the very least, we >>>> want to be able to build: >>>> >>>> 1) distribution from SVN (including actual SVN revision) >>>> 2) nightly build from SVN (ideally using actual SVN revision) >>>> 3) build from source >>>> 4) anything else? >>>> >>>> I think only 1) is currently working properly. >>>> >>>> 2) can be implemented by changing JMeterVersion to fix up the REVISION >>>> string, as was done originally. >>>> This will mean the workspace disagrees with SVN (unless we update SVN >>>> for every nightly build - seems like overkill), but there is no tag >>>> involved, and the source archive will agree with the build. >>>> >>>> 3) This used to use the current date as the version suffix. The idea >>>> being that the SVN revision is meaningless, so a date is better than >>>> nothing. >>>> >>>> In my opinion, the current state is a bit worse than before I tried to >>>> align SVN with the source archive, as local builds will display a >>>> misleading suffix. >>>> >>>> I'm not yet sure how to fix it, but unfortunately I think it may >>>> invalidate the current release candidate. >>>> >>>> On 9 August 2011 00:38, Milamber <[email protected]> wrote: >>>> >>>> >>>>> Hello, >>>>> >>>>> The second release candidate for JMeter 2.5 has been prepared, and your >>>>> votes are solicited. >>>>> >>>>> JMeter is a Java desktop application designed to load test functional >>>>> behavior and measure performance. The current version is targeted at >>>>> Java 1.5+. >>>>> >>>>> Archives/hashes/sigs: >>>>> http://people.apache.org/~milamber/jmeter-2.5RC2/dist >>>>> >>>>> MD5 hashes of archives for this vote: >>>>> >>>>> 1f8aaf3a2ab7206366a07c91bbafae55 *jakarta-jmeter-2.5.tgz >>>>> c557b3ff2c667693c8eb97cd67a09a95 *jakarta-jmeter-2.5.zip >>>>> 5c3bb2e583133adeff7f0d5668a1510a *jakarta-jmeter-2.5_src.tgz >>>>> ac98cd3a5603a70abac3be01897fb98c *jakarta-jmeter-2.5_src.zip >>>>> >>>>> Site Docs are here: >>>>> http://people.apache.org/~milamber/jmeter-2.5RC2/docs >>>>> >>>>> Tag: >>>>> http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_5_RC2 (r1155133) >>>>> >>>>> Keys are here: >>>>> http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ >>>>> also >>>>> http://people.apache.org/~milamber/ >>>>> >>>>> N.B. >>>>> To download the dependencies: "ant download_jars" >>>>> >>>>> To create the jars and test JMeter: "ant package test". >>>>> >>>>> JMeter 2.5 requires Java 1.5 or later. >>>>> >>>>> 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 1: on demand, if you want more time to test / verify this RC, the >>>>> delay can be increase. >>>>> >>>>> Note 2: some tests with JDK5/6/7 on Windows Seven and Mac OS X on new >>>>> functionality are welcome (httpclient 4.1 request, JMeter proxy with >>>>> httpclient java/hc3.1/hc4, Http request with parallels embedded >>>>> resources, View results tree, etc.) >>>>> >>>>> Note 3: 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 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>>> >>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
