Re: [Webtest] Can't build R_1689, but mostly works with latest build R_1724

[Vaughn Spurlin]

Hi Marc, We will proceed with WebTest 2.6 for now, to meet our schedule. It will be easy enough to upgrade to WebTest 3.0 when it's available. I will follow your advice for building R_1689, and ask for help with specific points if necessary. Thanks! - Vaughn Marc Guillemot wrote: Hi Vaughn, thinking at it again, I believe that the next release will be first available in the beginning of January. The reason is that it has to be 3.0 due to the upgrade from Java 1.4 to Java 5 and it is worth waiting for coming release 2.4 of HtmlUnit that provides (as usual) a lot of improvements. Once we think that a build is "ready" to be marked as "release" it doesn't take so much time but the right person (ie Dierk) must be available to do it. I fear that it will be too late for your build schedule and I first wanted to avoid that but because we haven't any release since the upgrade to Java 5, we can't simply put a minor release just now. You can get exactly the content of a release from SVN just looking at the tag (for instance R_1689 for WebTest 2.6). Nevertheless if you can't build from a src.zip, then it means that some files were missed while building the zip file and I would be happy to fix it if you can provide the right information. Cheers, Marc. Vaughn Spurlin wrote: Hi Marc, I would be much happier with a newer version of WebTest. However, "latest snapshot" is too fluid for our purpose. In order to create a stable environment when we gather a large number of open source tools, we need certainty that we will get the same results every time we retrieve a tool. Using a specific dot release, such as WebTest 2.6, generally satisfies our need for consistent results. Can you say when you will designate a 2.7 or 3.0 release? What would it take to trigger the dot release process? We need it soon to keep up with the Open Solaris build schedule. Of course, quality is paramount. It's better to miss a schedule than to miss the best available quality. Yes, a full build works as expected when I use svn to checkout and update the source. It does not work to download and unzip the latest snapshot zip files. Using svn to get the source gives many more files than unzipping the snapshot zip files. Suppose I need to build a specific dot release, such as 2.6 (or 2.7 when it's available). What should I do to build from downloaded zip files? Vaughn Hi, "official release"? By WebTest each build is nearly as official as the others. But I understand your problem, you're not the one that made this rule. May you have an incorrect version of Ant? Generally a full build should simply work with bin/webtest.[sh|bat] full and so does it on WebTest Cruise Control. Nevertheless release 2.6 is already quite old and it would surely be better if you could include a newer version of WebTest. When is the deadline for you? Cheers, Marc. -- Web: http://www.efficient-webtesting.com Blog: http://mguillem.wordpress.com Vaughn Spurlin wrote: Hello WebTest development team, I need to work with the latest Webtest official release, not the latest development build. Does build R_1689 use build instructions that are different from the latest development build? What's missing in my build environment? When I follow "Building WebTest with ant" instructions at http://webtest.canoo.com/webtest/manual/building.html with WebTest 2.6 source files from https://svn.canoo.com/trunk/webtest-releases/2.6-1689/, it fails ... (--- snip ---) _______________________________________________ WebTest mailing list WebTest@lists.canoo.com http://lists.canoo.com/mailman/listinfo/webtest _______________________________________________ WebTest mailing list WebTest@lists.canoo.com http://lists.canoo.com/mailman/listinfo/webtest _______________________________________________ WebTest mailing list WebTest@lists.canoo.com http://lists.canoo.com/mailman/listinfo/webtest