anwers inside:
--- Marc Guillemot <[email protected]> schrieb am Di, 17.2.2009: > in this mailing list??? nope, a personal one. ping him after not getting the registration mail for 2 hours. > > 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. > > 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 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. > > In the meantime, the latest version of the > webtest-maven-plugin can be downloaded from my git > http://ns1.backwork.net via > > > > $> git clone http://ns1.backwork.net/git/webtest- > > maven-plugin.git > > > > I don't like to upload this to the codehaus SVN > with those 3 jars :( > > That's the only thing which hinders us from an > 'official' maven release. > > It seems to me that a maven plugin should make usage of > webtest.xml and > from what I can see, this is not the case here. I can > imagine that it > has been written at a time where webtest.xml didn't > exist. I believe > that it would be better to start a new plugin from scratch > to use > webtest.xml correctly and to handle webtest tests written > in Groovy. What about 'old' projects? I e.g. have a lot of canoo-ant code lying around which has to be supported also. 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. WDYT? txs and LieGrue, strub _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
