>>> My problem is: currently those 3 jars are being >> repacked to the webtest-maven-plugin and codehaus folks will >> _not_ be very happy with that! >> >> 3 jars? >> There is no dependency against non released artifacts >> anymore. > > The webtest-maven-plugin currently has the following jars in it's lib > directory: > .) fontbox-0.1.0-dev-patched-20060622.jar > .) pdfbox-0.7.3-dev-log4j-20060612.jar > .) webtest-1720.jar > > can you point me to a current webtest jar so I can remove the other 2? > As I explained earlier: Although I use canoo, I'm not that deep into it like > Sigi. I'm only helping out a bit on the maven side because Sigi has not much > time currently.
you have to dowload the distribution from: http://webtest.canoo.com/webtest/manual/Downloads.html The webtest.jar is located in the lib folder There is no pom in the distribution but you can pick it from the sources: https://svn.canoo.com/trunk/webtest/pom.xml > >>> So what about doing a webtest-3.0-RC1 _now_ (this week >> at least)? So we at least have a preliminary version in the >> repo. >>> Maybe there are known bugs, but having this officially >> released will draw much attention and it can be used much >> more easily. >> >> I thought about that but it make first sense when there is >> really a >> Maven plugin available. > > I think the cat is biting in her tail here - not sure if this saying > translates well into english :) I don't know either if this is correct in english but it is fully ok when I translate it back in french ;-) > I can release (and even add it to SVN) only after I have a canoo webtest.jar > somewhere in an official repo which I can reference as dependency. Because I > don't like to add all thos 3-rd party jars to the apache SVN. > So after you published the jar to the public repo, I can push the > webtest-maven-plugin to codehaus.mojo as an 'official' maven plugin. I took > all the sources from Sigi and prepared them rdy for checkin. ok > ... > What about 'old' projects? I e.g. have a lot of canoo-ant code lying around > which has to be supported also. what kind of old projects? Before webtest.xml, users had to configure everything by themselves and there not really a "given" folder structure. This makes surely difficult for a maven plugin to work with all kinds of projects like this one. More generally, we should define for which kind of projects the plugin should work... and test it ;-) I see currently following cases: 1- tests in XML with a project using webtest.xml directly 2- tests in Groovy with a project using webtest.xml directly 3- tests in Groovy without direct usage of webtest.xml but only webtest as dependency In case (3) webtest will already be a dependency of the project and therefore doesn't need to be a dependency of the plugin (and should probably not). In case (1) it clearly needs to be provided by the plugin. In case (2)... it depends. > In either case, we have to get an initial version into SVN and then a lot of > people can contribute easily. > > There is an old english saying: How to climb a mountain? Step after Step! > > So my suggestion is: > 1.) publish a webtest-3.0.RC1.jar > 2.) I will checkin the current webtest-maven-plugin > 3.) we may then work together on getting it up to date. if this helps, I can publish build 1746. Cheers, Marc. -- Web: http://www.efficient-webtesting.com Blog: http://mguillem.wordpress.com _______________________________________________ WebTest mailing list WebTest@lists.canoo.com http://lists.canoo.com/mailman/listinfo/webtest
