Actually switching to emma got things working.. I just start jetty from the base class of my selenium test. I have a static field that prevents jetty from attempting to start twice.
Seems to work great. D/ On Mar 4, 2010, at 11:23 PM, hanasaki wrote: > most of what I have found points to using emma to get code coverage in > the integration phase using the failsafe plugin and embedded Jetty. > > -------- Original Message -------- > Subject: cobertura & jetty > From: Douglas Ferguson <doug...@douglasferguson.us> > To: Maven Users List <users@maven.apache.org> > Date: 03/04/2010 10:43 PM > >> So I finally got jetty starting from my test case, but it doesn't >> impact the code coverage. >> >> My BasePage class is at 0% which is confusing. >> >> The server is started from the test class which would make you think >> would be using the instrumented classes and jetty would inherit the >> same classpath. >> >> What am I missing? >> >> Douglas >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For >> additional commands, e-mail: users-h...@maven.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
