I had a look at the code a while ago - the problem is that there is no way to (programatically) specify a filter to apply to the test phase.
There's an open JIRA to do with configuring the classpath for surefire - either will be able to generate a solution. On 07/02/06, Mike Perham <[EMAIL PROTECTED]> wrote: > Only the actual Cobertura jar is needed during test, just like Clover. > Note in MEV-321 that Carlos's solution excludes every dep. The issue is > that CoberturaInstrumentMojo.addCoberturaDependenciesToTestClasspath() > adds the cobertura artifact in such a manner that transitive deps are > pulled in also. If we can disable that transitivity somehow, that will > solve the problem and the phony cobertura-runtime POM will not be > necessary. > > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 07, 2006 8:25 AM > To: [email protected] > Subject: Re: [mojo-dev] Re: [mojo-scm] [1445] > trunk/mojo/mojo-sandbox/cobertura-maven-plugin: PR: MOJO-226 > > > I think I'm starting to understand a bit better. I was just a bit thrown > by a dummy dependency, and wonder if there isn't a better way. Maybe we > just need to select the explicit cobertura deps to include on the > runtime classpath? >
