oops - apologies... I just took a look at tapestry-test (and other subprojects) and didn't see anything using selenium-java-client-driver + hudson is correctly building everything.
So, i don't know if selenium-java-client-driver was a dependency before, but it's not now (and rightly so). On Tue, Mar 23, 2010 at 16:52, Robin Komiwes <odiss...@gmail.com> wrote: > Just to be clear, the class I was speaking about belongs to > org.apache.tapestry5 (tapestry-test artifact). > > Anyway, I will try "mvn dependency:analyze" later and give feedback. > > Thanx! > > On Tuesday, March 23, 2010, Andreas Andreou <andy...@di.uoa.gr> wrote: >> Robin, if your project directly uses selenium classes, then you should >> add that dependency >> in any case. It's bad practice to directly use transitive >> dependencies, because it's easy to end up >> in such problems... >> >> To give another example, tapestry-core now uses some commons-codec classes - >> perhaps in the future in order to decrease download size or do perf. >> optimization, tapestry decides >> to drop that dependency and implement whatever it needs on its own - >> so, if other projects also >> need commons-codedc, they should include it themselves, not rely on >> tapestry, e.t.c. >> >> Anyway, try running "mvn dependency:analyze" to see a report of used >> undeclared dependencies >> and unused declared dependencies in your project >> >> On Tue, Mar 23, 2010 at 14:34, Ulrich Stärk <u...@spielviel.de> wrote: >>> Might be that I messed something up when upgrading the selenium-versions >>> some time ago. I will look into it. >>> >>> Uli >>> >>> On 23.03.2010 13:18, Robin Komiwes wrote: >>>> >>>> Hi, >>>> >>>> We are currently integrating Tapestry 5.2.0-SNAPSHOT for Wooki. When I >>>> changed Tapestry version in our pom.xml I had a compilation problem >>>> with some imports related to tapestry-test (in fact, when our test >>>> classes were extending SeleniumTestCase). >>>> >>>> To fix them I had to add the following dependency: >>>> >>>> >>>> <dependency> >>>> <groupId>org.seleniumhq.selenium.client-drivers</groupId> >>>> <artifactId>selenium-java-client-driver</artifactId> >>>> <version>1.0.1</version> >>>> <scope>test</scope> >>>> </dependency> >>>> >>>> It may be my fault, it may be related to the newly missing formos >>>> repository, or maybe there is something else. >>>> >>>> Any pointer on that? >>>> >>>> Regards, >>>> >>>> Robin >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>> For additional commands, e-mail: users-h...@tapestry.apache.org >>> >>> >> >> >> >> -- >> Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr >> Tapestry / Tacos developer >> Open Source / JEE Consulting >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
