Hi, I agree that the build is probably too complicated and that simplifications would be welcome but I don't necessarily agree on your points, see below.
Yoo-Jin Lee wrote: > Here's some thoughts to simplify the build: > > 1. put all libs (including test) in repository (you already have many > libs in your repository) > a. maybe in \webtest\lib\build' no. The dependencies are maintained à la maven through the pom. In fact some of the libs in webtest/lib could probably be removed and fetched. > 2. remove fetchDependencies from maven -> I'm behind a proxy and > fetchDependencies continually fails. I had to download maven, setup the > proxy fields and then manually add each lib - very painfull! as far as I remember, you just have to configure your proxy settings in ~/.m2/settings.xml. That's all. Can you please check that and I'll update the documentation. > > 3. update webtest\bin\webtest.bat > a. do not depend on WEBTEST_HOME to point to a build of webtest and > it's dependant libs (doesn't this defeat the purpose of the build?? You > should be able to download trunk and the build should just work) hmm, why do you say that it depends on WEBTEST_HOME? The bat file contains set WEBTEST_HOME=%~dp0%.. which means that WEBTEST_HOME is determined as parent dir of the webtest.bat script. > I think if you can simplify the build you'd get more people to help out... I fully agree. I had the same problem when I wanted to propose my first patch to WebTest (a long long time ago) and didn't want to put html test code in a java servlet. Have you some special ideas? Cheers, Marc. -- Blog: http://mguillem.wordpress.com _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
